From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"Biggers, Caleb" <caleb.biggers@intel.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"irogers@google.com" <irogers@google.com>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"Baker, Edward" <edward.baker@intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"mani@kernel.org" <mani@kernel.org>,
"acme@kernel.org" <acme@kernel.org>,
"afaerber@suse.de" <afaerber@suse.de>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>
Subject: Re: [PATCH v1 00/15] perf vendor events: Update Intel events
Date: Mon, 30 Jun 2025 14:21:19 +0000 [thread overview]
Message-ID: <fe821704ddd4a3ae5169ec974cc8cfde8dc44e7d.camel@intel.com> (raw)
In-Reply-To: <CAP-5=fVGqnWuQNYM9XULyLuDvx-yAuyCMRh=uS0gybiEsYH9jw@mail.gmail.com>
On Fri, 2025-06-27 at 17:15 -0700, Ian Rogers wrote:
> On Wed, Jun 11, 2025 at 5:02 PM Ian Rogers <irogers@google.com> wrote:
> >
> > Update:
> > - ADL/ADLN v1.29 -> 1.31
> > - ARL 1.08 -> 1.09
> > - CLX 1.23 -> 1.25
> > - EMR 1.11 -> 1.14
> > - GRR 1.07 -> 1.09
> > - GNR 1.08 -> 1.10
> > - ICX 1.27 -> 1.28
> > - LNL 1.11 -> 1.14
> > - MTL 1.13 -> 1.14
> > - PTL new v1.00
> > - SPR 1.25 -> 1.28
> > - SRF 1.09 -> 1.11
> > - SKX 1.36 -> 1.37
> > - TGL 1.17 -> 1.18
> >
> > Updates from:
> > https://github.com/intel/perfmon
> > with:
> > https://github.com/intel/perfmon/pull/312
> > Running the script:
> > https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
>
> Hi, these Intel event updates are still awaiting review.
>
> Thanks,
> Ian
Hi Ian, not sure what happened but I can't find this series in my inbox. Could you resend it?
Thanks,
Tom
>
> > Ian Rogers (15):
> > perf vendor events: Update Alderlake events
> > perf vendor events: Update AlderlakeN events
> > perf vendor events: Update Arrowlake events
> > perf vendor events: Update CascadelakeX events
> > perf vendor events: Update EmeraldRapids events
> > perf vendor events: Update GrandRidge events
> > perf vendor events: Update GraniteRapids events
> > perf vendor events: Update IcelakeX events
> > perf vendor events: Update LunarLake events
> > perf vendor events: Update MeteorLake events
> > perf vendor events: Add PantherLake events
> > perf vendor events: Update SapphireRapids events
> > perf vendor events: Update SierraForest events
> > perf vendor events: Update SkylakeX events
> > perf vendor events: Update TigerLake events
> >
> > .../pmu-events/arch/x86/alderlake/cache.json | 56 ++-
> > .../arch/x86/alderlake/floating-point.json | 1 -
> > .../pmu-events/arch/x86/alderlake/other.json | 1 -
> > .../arch/x86/alderlake/pipeline.json | 44 +--
> > .../arch/x86/alderlake/virtual-memory.json | 3 -
> > .../pmu-events/arch/x86/alderlaken/cache.json | 52 +--
> > .../arch/x86/alderlaken/floating-point.json | 1 -
> > .../pmu-events/arch/x86/alderlaken/other.json | 1 -
> > .../arch/x86/alderlaken/pipeline.json | 42 +--
> > .../arch/x86/alderlaken/virtual-memory.json | 3 -
> > .../pmu-events/arch/x86/arrowlake/cache.json | 13 +-
> > .../arch/x86/arrowlake/frontend.json | 135 ++++++++
> > .../arch/x86/cascadelakex/floating-point.json | 6 +-
> > .../arch/x86/cascadelakex/pipeline.json | 2 +-
> > .../arch/x86/emeraldrapids/pipeline.json | 2 +-
> > .../arch/x86/emeraldrapids/uncore-io.json | 12 +
> > .../arch/x86/emeraldrapids/uncore-memory.json | 20 ++
> > .../arch/x86/grandridge/grr-metrics.json | 30 +-
> > .../x86/grandridge/uncore-interconnect.json | 10 +
> > .../arch/x86/grandridge/uncore-io.json | 12 +
> > .../arch/x86/graniterapids/cache.json | 9 +
> > .../arch/x86/graniterapids/counter.json | 10 +-
> > .../arch/x86/graniterapids/gnr-metrics.json | 36 ++
> > .../arch/x86/graniterapids/pipeline.json | 2 +-
> > .../graniterapids/uncore-interconnect.json | 19 -
> > .../arch/x86/graniterapids/uncore-io.json | 27 +-
> > .../arch/x86/icelakex/pipeline.json | 2 +-
> > .../arch/x86/icelakex/uncore-cache.json | 2 -
> > .../pmu-events/arch/x86/lunarlake/cache.json | 11 +
> > .../arch/x86/lunarlake/pipeline.json | 18 +-
> > .../arch/x86/lunarlake/virtual-memory.json | 18 -
> > tools/perf/pmu-events/arch/x86/mapfile.csv | 29 +-
> > .../pmu-events/arch/x86/meteorlake/cache.json | 2 +-
> > .../arch/x86/meteorlake/frontend.json | 72 ++++
> > .../arch/x86/meteorlake/pipeline.json | 2 +-
> > .../arch/x86/pantherlake/cache.json | 278 +++++++++++++++
> > .../arch/x86/pantherlake/counter.json | 12 +
> > .../arch/x86/pantherlake/frontend.json | 30 ++
> > .../arch/x86/pantherlake/memory.json | 215 ++++++++++++
> > .../arch/x86/pantherlake/pipeline.json | 325 ++++++++++++++++++
> > .../arch/x86/pantherlake/virtual-memory.json | 62 ++++
> > .../arch/x86/sapphirerapids/pipeline.json | 2 +-
> > .../arch/x86/sapphirerapids/uncore-io.json | 12 +
> > .../x86/sapphirerapids/uncore-memory.json | 20 ++
> > .../arch/x86/sierraforest/frontend.json | 64 ++++
> > .../arch/x86/sierraforest/pipeline.json | 8 +
> > .../arch/x86/sierraforest/srf-metrics.json | 48 +++
> > .../arch/x86/sierraforest/uncore-cache.json | 6 +-
> > .../x86/sierraforest/uncore-interconnect.json | 53 ++-
> > .../arch/x86/sierraforest/uncore-io.json | 27 +-
> > .../arch/x86/skylakex/pipeline.json | 2 +-
> > .../arch/x86/tigerlake/pipeline.json | 2 +-
> > 52 files changed, 1623 insertions(+), 248 deletions(-)
> > create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/cache.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/counter.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/frontend.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/memory.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/pipeline.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/virtual-memory.json
> >
> > --
> > 2.50.0.rc1.591.g9c95f17f64-goog
> >
next prev parent reply other threads:[~2025-06-30 14:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 0:02 [PATCH v1 00/15] perf vendor events: Update Intel events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 01/15] perf vendor events: Update Alderlake events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 02/15] perf vendor events: Update AlderlakeN events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 03/15] perf vendor events: Update Arrowlake events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 04/15] perf vendor events: Update CascadelakeX events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 05/15] perf vendor events: Update EmeraldRapids events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 06/15] perf vendor events: Update GrandRidge events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 07/15] perf vendor events: Update GraniteRapids events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 08/15] perf vendor events: Update IcelakeX events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 09/15] perf vendor events: Update LunarLake events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 10/15] perf vendor events: Update MeteorLake events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 11/15] perf vendor events: Add PantherLake events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 12/15] perf vendor events: Update SapphireRapids events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 13/15] perf vendor events: Update SierraForest events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 14/15] perf vendor events: Update SkylakeX events Ian Rogers
2025-06-12 0:02 ` [PATCH v1 15/15] perf vendor events: Update TigerLake events Ian Rogers
2025-06-28 0:15 ` [PATCH v1 00/15] perf vendor events: Update Intel events Ian Rogers
2025-06-30 14:21 ` Falcon, Thomas [this message]
2025-06-30 15:39 ` Ian Rogers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe821704ddd4a3ae5169ec974cc8cfde8dc44e7d.camel@intel.com \
--to=thomas.falcon@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).