From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "linux-actions@lists.infradead.org"
<linux-actions@lists.infradead.org>,
"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>,
"peterz@infradead.org" <peterz@infradead.org>,
"Wang, Weilin" <weilin.wang@intel.com>,
"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>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1 00/19] Intel TMA 5.1 metrics and event updates
Date: Tue, 22 Jul 2025 18:14:30 +0000 [thread overview]
Message-ID: <e09bab119c9fb6b0c2b5bcd39c6f2b508445ca37.camel@intel.com> (raw)
In-Reply-To: <20250719034515.2000467-1-irogers@google.com>
On Fri, 2025-07-18 at 20:44 -0700, Ian Rogers wrote:
> Update events from:
> v1.31 -> v1.33 for alderlake
> v1.09 -> v1.12 for arrowlake
> v1.14 -> v1.16 for emeraldrapids
> v1.10 -> v1.12 for graniterpaids
> v1.14 -> v1.17 for lunarlake
> v1.14 -> v1.16 for meteorlake
> v1.28 -> v1.30 for sapphirerapids
>
> Update TMA 5.0 to 5.1 removing the slots event workaround as the patch series:
> https://lore.kernel.org/lkml/20250719030517.1990983-1-irogers@google.com/
> is assumed.
>
> The patches are generated by:
> https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
> with pull requests 323 and 324 applied.
>
Hi Ian, metrics tests look good on my alder lake and arrow lake.
Tested-by: Thomas Falcon <thomas.falcon@intel.com>
Thanks,
Tom
> Ian Rogers (19):
> perf vendor events: Update alderlake events/metrics
> perf vendor events: Update arrowlake events/metrics
> perf vendor events: Update broadwell metrics
> perf vendor events: Update cascadelakex metrics
> perf vendor events: Update emeraldrapids events/metrics
> perf vendor events: Update grandridge metrics
> perf vendor events: Update graniterapids events/metrics
> perf vendor events: Update haswell metrics
> perf vendor events: Update icelake metrics
> perf vendor events: Update ivybridge/ivytown metrics
> perf vendor events: Update jaketown metrics
> perf vendor events: Update lunarlake events/metrics
> perf vendor events: Update meteorlake events/metrics
> perf vendor events: Update rocketlake metrics
> perf vendor events: Update sandybridge metrics
> perf vendor events: Update sapphirerapids events/metrics
> perf vendor events: Update sierraforest metrics
> perf vendor events: Update skylake metrics
> perf vendor events: Update tigerlake metrics
>
> .../arch/x86/alderlake/adl-metrics.json | 104 ++++----
> .../pmu-events/arch/x86/alderlake/cache.json | 99 ++++----
> .../arch/x86/alderlake/floating-point.json | 28 +--
> .../arch/x86/alderlake/frontend.json | 42 ++--
> .../pmu-events/arch/x86/alderlake/memory.json | 12 +-
> .../pmu-events/arch/x86/alderlake/other.json | 8 +-
> .../arch/x86/alderlake/pipeline.json | 163 +++++--------
> .../x86/alderlake/uncore-interconnect.json | 2 -
> .../arch/x86/alderlake/virtual-memory.json | 40 +--
> .../arch/x86/alderlaken/adln-metrics.json | 20 +-
> .../x86/alderlaken/uncore-interconnect.json | 2 -
> .../arch/x86/arrowlake/arl-metrics.json | 180 ++++++++------
> .../pmu-events/arch/x86/arrowlake/cache.json | 122 +++++++---
> .../arch/x86/arrowlake/frontend.json | 40 +--
> .../pmu-events/arch/x86/arrowlake/memory.json | 22 +-
> .../arch/x86/arrowlake/pipeline.json | 94 +++++---
> .../arch/x86/broadwell/bdw-metrics.json | 30 +--
> .../arch/x86/broadwellde/bdwde-metrics.json | 30 +--
> .../arch/x86/broadwellx/bdx-metrics.json | 33 ++-
> .../arch/x86/cascadelakex/clx-metrics.json | 139 ++++++++---
> .../arch/x86/emeraldrapids/cache.json | 100 ++++----
> .../arch/x86/emeraldrapids/emr-metrics.json | 131 +++++-----
> .../x86/emeraldrapids/floating-point.json | 43 ++--
> .../arch/x86/emeraldrapids/frontend.json | 42 ++--
> .../arch/x86/emeraldrapids/memory.json | 30 +--
> .../arch/x86/emeraldrapids/other.json | 28 ++-
> .../arch/x86/emeraldrapids/pipeline.json | 167 +++++--------
> .../arch/x86/emeraldrapids/uncore-memory.json | 82 +++++++
> .../x86/emeraldrapids/virtual-memory.json | 40 +--
> .../arch/x86/grandridge/grr-metrics.json | 20 +-
> .../arch/x86/graniterapids/cache.json | 227 +++++++++++++-----
> .../x86/graniterapids/floating-point.json | 43 ++--
> .../arch/x86/graniterapids/frontend.json | 42 ++--
> .../arch/x86/graniterapids/gnr-metrics.json | 131 +++++-----
> .../arch/x86/graniterapids/memory.json | 33 ++-
> .../arch/x86/graniterapids/other.json | 30 ++-
> .../arch/x86/graniterapids/pipeline.json | 167 ++++++-------
> .../arch/x86/graniterapids/uncore-io.json | 1 -
> .../arch/x86/graniterapids/uncore-memory.json | 31 ---
> .../x86/graniterapids/virtual-memory.json | 40 +--
> .../arch/x86/haswell/hsw-metrics.json | 32 ++-
> .../arch/x86/haswellx/hsx-metrics.json | 35 ++-
> .../arch/x86/icelake/icl-metrics.json | 96 ++++----
> .../arch/x86/icelakex/icx-metrics.json | 155 ++++++++----
> .../arch/x86/ivybridge/ivb-metrics.json | 30 +--
> .../arch/x86/ivytown/ivt-metrics.json | 33 ++-
> .../arch/x86/jaketown/jkt-metrics.json | 20 +-
> .../pmu-events/arch/x86/lunarlake/cache.json | 104 ++++++--
> .../arch/x86/lunarlake/frontend.json | 40 +--
> .../arch/x86/lunarlake/lnl-metrics.json | 216 +++++++++--------
> .../pmu-events/arch/x86/lunarlake/memory.json | 22 +-
> .../arch/x86/lunarlake/pipeline.json | 85 ++++---
> .../x86/lunarlake/uncore-interconnect.json | 10 +
> .../arch/x86/lunarlake/uncore-memory.json | 8 +
> tools/perf/pmu-events/arch/x86/mapfile.csv | 16 +-
> .../pmu-events/arch/x86/meteorlake/cache.json | 129 +++++-----
> .../arch/x86/meteorlake/floating-point.json | 28 +--
> .../arch/x86/meteorlake/frontend.json | 42 ++--
> .../arch/x86/meteorlake/memory.json | 15 +-
> .../arch/x86/meteorlake/mtl-metrics.json | 103 ++++----
> .../pmu-events/arch/x86/meteorlake/other.json | 5 +-
> .../arch/x86/meteorlake/pipeline.json | 173 ++++++-------
> .../arch/x86/meteorlake/virtual-memory.json | 40 +--
> .../arch/x86/rocketlake/rkl-metrics.json | 97 ++++----
> .../arch/x86/sandybridge/snb-metrics.json | 19 +-
> .../arch/x86/sapphirerapids/cache.json | 100 ++++----
> .../x86/sapphirerapids/floating-point.json | 43 ++--
> .../arch/x86/sapphirerapids/frontend.json | 42 ++--
> .../arch/x86/sapphirerapids/memory.json | 30 +--
> .../arch/x86/sapphirerapids/other.json | 28 ++-
> .../arch/x86/sapphirerapids/pipeline.json | 167 +++++--------
> .../arch/x86/sapphirerapids/spr-metrics.json | 153 +++++++-----
> .../x86/sapphirerapids/uncore-memory.json | 82 +++++++
> .../x86/sapphirerapids/virtual-memory.json | 40 +--
> .../arch/x86/sierraforest/srf-metrics.json | 20 +-
> .../arch/x86/skylake/skl-metrics.json | 101 +++++---
> .../arch/x86/skylakex/skx-metrics.json | 101 +++++---
> .../arch/x86/tigerlake/tgl-metrics.json | 97 ++++----
> 78 files changed, 2870 insertions(+), 2325 deletions(-)
> create mode 100644 tools/perf/pmu-events/arch/x86/lunarlake/uncore-interconnect.json
>
next prev parent reply other threads:[~2025-07-22 18:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 3:44 [PATCH v1 00/19] Intel TMA 5.1 metrics and event updates Ian Rogers
2025-07-19 3:44 ` [PATCH v1 03/19] perf vendor events: Update broadwell metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 04/19] perf vendor events: Update cascadelakex metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 06/19] perf vendor events: Update grandridge metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 08/19] perf vendor events: Update haswell metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 09/19] perf vendor events: Update icelake metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 10/19] perf vendor events: Update ivybridge/ivytown metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 11/19] perf vendor events: Update jaketown metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 14/19] perf vendor events: Update rocketlake metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 15/19] perf vendor events: Update sandybridge metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 17/19] perf vendor events: Update sierraforest metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 18/19] perf vendor events: Update skylake metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 19/19] perf vendor events: Update tigerlake metrics Ian Rogers
2025-07-22 18:14 ` Falcon, Thomas [this message]
2025-07-23 1:05 ` [PATCH v1 00/19] Intel TMA 5.1 metrics and event updates Namhyung Kim
2025-07-26 22:34 ` Namhyung Kim
2025-07-28 18:12 ` Namhyung Kim
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=e09bab119c9fb6b0c2b5bcd39c6f2b508445ca37.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=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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 \
--cc=weilin.wang@intel.com \
/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).