From: Ian Rogers <irogers@google.com>
To: "Thomas Falcon" <thomas.falcon@intel.com>,
"Perry Taylor" <perry.taylor@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Ian Rogers" <irogers@google.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Caleb Biggers" <caleb.biggers@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH v2 00/10] perf vendor events intel update
Date: Thu, 25 Sep 2025 10:27:26 -0700 [thread overview]
Message-ID: <20250925172736.960368-1-irogers@google.com> (raw)
Update events and some metrics to the latest perfmon versions:
- alderlake 1.34
- arrowlake 1.13
- emeraldrapids 1.20
- grandridge 1.10
- graniterapids 1.15
- lunarlake 1.18
- meteorlake 1.17
- sapphirerapids 1.35
- sierraforest 1.12
v2: EMR/SPR cpu_cstate metric fixes.
Ian Rogers (10):
perf vendor events intel: Update alderlake events to v1.34
perf vendor events intel: Update arrowlake events to v1.13
perf vendor events intel: Update emeraldrapids events to v1.20
perf vendor events intel: Update grandridge events to v1.10
perf vendor events intel: Update graniterapids events to v1.15
perf vendor events intel: Update lunarlake events to v1.18
perf vendor events intel: Update meteorlake events to v1.17
perf vendor events intel: Update pantherlake events to v1.00
perf vendor events intel: Update sapphirerapids events to v1.35
perf vendor events intel: Update sierraforest events to v1.12
.../pmu-events/arch/x86/alderlake/cache.json | 36 +
.../pmu-events/arch/x86/arrowlake/cache.json | 46 +-
.../pmu-events/arch/x86/arrowlake/memory.json | 6 +-
.../pmu-events/arch/x86/arrowlake/other.json | 2 +-
.../arch/x86/emeraldrapids/cache.json | 63 +
.../arch/x86/emeraldrapids/emr-metrics.json | 12 +
.../arch/x86/emeraldrapids/uncore-cache.json | 11 +
.../arch/x86/emeraldrapids/uncore-memory.json | 22 +
.../arch/x86/emeraldrapids/uncore-power.json | 2 -
.../pmu-events/arch/x86/grandridge/cache.json | 20 +-
.../graniterapids/uncore-interconnect.json | 10 +-
.../arch/x86/graniterapids/uncore-memory.json | 112 ++
.../pmu-events/arch/x86/lunarlake/cache.json | 46 +-
.../pmu-events/arch/x86/lunarlake/memory.json | 6 +-
.../pmu-events/arch/x86/lunarlake/other.json | 2 +-
tools/perf/pmu-events/arch/x86/mapfile.csv | 20 +-
.../pmu-events/arch/x86/meteorlake/cache.json | 36 +
.../arch/x86/pantherlake/cache.json | 1207 ++++++++++-
.../arch/x86/pantherlake/counter.json | 9 +-
.../arch/x86/pantherlake/floating-point.json | 286 +++
.../arch/x86/pantherlake/frontend.json | 535 +++++
.../arch/x86/pantherlake/memory.json | 106 +-
.../arch/x86/pantherlake/other.json | 44 +
.../arch/x86/pantherlake/pipeline.json | 1776 ++++++++++++++++-
.../arch/x86/pantherlake/uncore-memory.json | 26 +
.../arch/x86/pantherlake/virtual-memory.json | 248 +++
.../arch/x86/sapphirerapids/cache.json | 63 +
.../arch/x86/sapphirerapids/spr-metrics.json | 12 +
.../arch/x86/sapphirerapids/uncore-cache.json | 11 +
.../x86/sapphirerapids/uncore-memory.json | 22 +
.../arch/x86/sapphirerapids/uncore-power.json | 2 -
.../arch/x86/sierraforest/cache.json | 61 +-
.../x86/sierraforest/uncore-interconnect.json | 10 +-
.../arch/x86/sierraforest/uncore-io.json | 1 -
.../arch/x86/sierraforest/uncore-memory.json | 103 +-
35 files changed, 4712 insertions(+), 262 deletions(-)
create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/floating-point.json
create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/other.json
create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/uncore-memory.json
--
2.51.0.536.g15c5d4f767-goog
next reply other threads:[~2025-09-25 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 17:27 Ian Rogers [this message]
2025-09-25 17:27 ` [PATCH v2 01/10] perf vendor events intel: Update alderlake events to v1.34 Ian Rogers
2025-09-25 17:27 ` [PATCH v2 02/10] perf vendor events intel: Update arrowlake events to v1.13 Ian Rogers
2025-09-25 17:27 ` [PATCH v2 03/10] perf vendor events intel: Update emeraldrapids events to v1.20 Ian Rogers
2025-09-29 23:45 ` Falcon, Thomas
2025-09-30 16:26 ` Arnaldo Carvalho de Melo
2025-09-30 17:31 ` Falcon, Thomas
2025-09-25 17:27 ` [PATCH v2 04/10] perf vendor events intel: Update grandridge events to v1.10 Ian Rogers
2025-09-25 17:27 ` [PATCH v2 05/10] perf vendor events intel: Update graniterapids events to v1.15 Ian Rogers
2025-09-25 17:27 ` [PATCH v2 06/10] perf vendor events intel: Update lunarlake events to v1.18 Ian Rogers
2025-09-25 17:27 ` [PATCH v2 07/10] perf vendor events intel: Update meteorlake events to v1.17 Ian Rogers
2025-09-25 17:27 ` [PATCH v2 08/10] perf vendor events intel: Update pantherlake events to v1.00 Ian Rogers
2025-09-25 17:27 ` [PATCH v2 09/10] perf vendor events intel: Update sapphirerapids events to v1.35 Ian Rogers
2025-09-25 17:27 ` [PATCH v2 10/10] perf vendor events intel: Update sierraforest events to v1.12 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=20250925172736.960368-1-irogers@google.com \
--to=irogers@google.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=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=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.