From: Ian Rogers <irogers@google.com>
To: "Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"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" <manivannan.sadhasivam@linaro.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Caleb Biggers" <caleb.biggers@intel.com>,
"Weilin Wang" <weilin.wang@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Perry Taylor" <perry.taylor@intel.com>,
"Thomas Falcon" <thomas.falcon@intel.com>
Subject: [PATCH v1 24/35] perf vendor events: Update nehalemex events
Date: Fri, 21 Mar 2025 23:33:52 -0700 [thread overview]
Message-ID: <20250322063403.364981-25-irogers@google.com> (raw)
In-Reply-To: <20250322063403.364981-1-irogers@google.com>
Update event topic moving other topic events to cache and virtual
memory.
Signed-off-by: Ian Rogers <irogers@google.com>
---
.../pmu-events/arch/x86/nehalemex/cache.json | 32 +++++++++++++++
.../pmu-events/arch/x86/nehalemex/other.json | 40 -------------------
.../arch/x86/nehalemex/virtual-memory.json | 8 ++++
3 files changed, 40 insertions(+), 40 deletions(-)
diff --git a/tools/perf/pmu-events/arch/x86/nehalemex/cache.json b/tools/perf/pmu-events/arch/x86/nehalemex/cache.json
index 2c0ea6f8c4e0..b6c6b22a3188 100644
--- a/tools/perf/pmu-events/arch/x86/nehalemex/cache.json
+++ b/tools/perf/pmu-events/arch/x86/nehalemex/cache.json
@@ -239,6 +239,38 @@
"SampleAfterValue": "100000",
"UMask": "0x2"
},
+ {
+ "BriefDescription": "L1I instruction fetch stall cycles",
+ "Counter": "0,1,2,3",
+ "EventCode": "0x80",
+ "EventName": "L1I.CYCLES_STALLED",
+ "SampleAfterValue": "2000000",
+ "UMask": "0x4"
+ },
+ {
+ "BriefDescription": "L1I instruction fetch hits",
+ "Counter": "0,1,2,3",
+ "EventCode": "0x80",
+ "EventName": "L1I.HITS",
+ "SampleAfterValue": "2000000",
+ "UMask": "0x1"
+ },
+ {
+ "BriefDescription": "L1I instruction fetch misses",
+ "Counter": "0,1,2,3",
+ "EventCode": "0x80",
+ "EventName": "L1I.MISSES",
+ "SampleAfterValue": "2000000",
+ "UMask": "0x2"
+ },
+ {
+ "BriefDescription": "L1I Instruction fetches",
+ "Counter": "0,1,2,3",
+ "EventCode": "0x80",
+ "EventName": "L1I.READS",
+ "SampleAfterValue": "2000000",
+ "UMask": "0x3"
+ },
{
"BriefDescription": "All L2 data requests",
"Counter": "0,1,2,3",
diff --git a/tools/perf/pmu-events/arch/x86/nehalemex/other.json b/tools/perf/pmu-events/arch/x86/nehalemex/other.json
index f6887b234b0e..5fe5ca778e9f 100644
--- a/tools/perf/pmu-events/arch/x86/nehalemex/other.json
+++ b/tools/perf/pmu-events/arch/x86/nehalemex/other.json
@@ -15,46 +15,6 @@
"SampleAfterValue": "2000000",
"UMask": "0x1"
},
- {
- "BriefDescription": "L1I instruction fetch stall cycles",
- "Counter": "0,1,2,3",
- "EventCode": "0x80",
- "EventName": "L1I.CYCLES_STALLED",
- "SampleAfterValue": "2000000",
- "UMask": "0x4"
- },
- {
- "BriefDescription": "L1I instruction fetch hits",
- "Counter": "0,1,2,3",
- "EventCode": "0x80",
- "EventName": "L1I.HITS",
- "SampleAfterValue": "2000000",
- "UMask": "0x1"
- },
- {
- "BriefDescription": "L1I instruction fetch misses",
- "Counter": "0,1,2,3",
- "EventCode": "0x80",
- "EventName": "L1I.MISSES",
- "SampleAfterValue": "2000000",
- "UMask": "0x2"
- },
- {
- "BriefDescription": "L1I Instruction fetches",
- "Counter": "0,1,2,3",
- "EventCode": "0x80",
- "EventName": "L1I.READS",
- "SampleAfterValue": "2000000",
- "UMask": "0x3"
- },
- {
- "BriefDescription": "Large ITLB hit",
- "Counter": "0,1,2,3",
- "EventCode": "0x82",
- "EventName": "LARGE_ITLB.HIT",
- "SampleAfterValue": "200000",
- "UMask": "0x1"
- },
{
"BriefDescription": "All loads dispatched",
"Counter": "0,1,2,3",
diff --git a/tools/perf/pmu-events/arch/x86/nehalemex/virtual-memory.json b/tools/perf/pmu-events/arch/x86/nehalemex/virtual-memory.json
index e88c0802e679..accd263cfbfd 100644
--- a/tools/perf/pmu-events/arch/x86/nehalemex/virtual-memory.json
+++ b/tools/perf/pmu-events/arch/x86/nehalemex/virtual-memory.json
@@ -88,6 +88,14 @@
"SampleAfterValue": "200000",
"UMask": "0x20"
},
+ {
+ "BriefDescription": "Large ITLB hit",
+ "Counter": "0,1,2,3",
+ "EventCode": "0x82",
+ "EventName": "LARGE_ITLB.HIT",
+ "SampleAfterValue": "200000",
+ "UMask": "0x1"
+ },
{
"BriefDescription": "Retired loads that miss the DTLB (Precise Event)",
"Counter": "0,1,2,3",
--
2.49.0.395.g12beb8f557-goog
next prev parent reply other threads:[~2025-03-22 6:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 6:33 [PATCH v1 00/35] GNR retirement latencies, topic and metric updates Ian Rogers
2025-03-22 6:33 ` [PATCH v1 01/35] perf vendor events: Update alderlake events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 02/35] perf vendor events: Update AlderlakeN events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 03/35] perf vendor events: Update arrowlake events/metrics Ian Rogers
2025-03-25 0:16 ` Falcon, Thomas
2025-03-25 15:09 ` Ian Rogers
2025-03-22 6:33 ` [PATCH v1 04/35] perf vendor events: Update bonnell events Ian Rogers
2025-03-22 6:33 ` [PATCH v1 05/35] perf vendor events: Update broadwell metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 06/35] perf vendor events: Update broadwellde metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 07/35] perf vendor events: Update broadwellx metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 08/35] perf vendor events: Update cascadelakex events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 09/35] perf vendor events: Update clearwaterforest events Ian Rogers
2025-03-22 6:33 ` [PATCH v1 10/35] perf vendor events: Update elkhartlake events Ian Rogers
2025-03-22 6:33 ` [PATCH v1 11/35] perf vendor events: Update emeraldrapids events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 12/35] perf vendor events: Update grandridge events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 13/35] perf vendor events: Add graniterapids retirement latencies Ian Rogers
2025-03-22 6:33 ` [PATCH v1 14/35] perf vendor events: Update haswell metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 15/35] perf vendor events: Update haswellx metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 16/35] perf vendor events: Update icelake events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 17/35] perf vendor events: Update icelakex events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 18/35] perf vendor events: Update ivybridge metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 19/35] perf vendor events: Update ivytown metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 20/35] perf vendor events: Update jaketown metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 21/35] perf vendor events: Update lunarlake events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 22/35] perf vendor events: Update meteorlake events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 23/35] perf vendor events: Update nehalemep events Ian Rogers
2025-03-22 6:33 ` Ian Rogers [this message]
2025-03-22 6:33 ` [PATCH v1 25/35] perf vendor events: Update rocketlake events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 26/35] perf vendor events: Update sandybridge metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 27/35] perf vendor events: Update sapphirerapids events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 28/35] perf vendor events: Update sierraforest events Ian Rogers
2025-03-22 6:33 ` [PATCH v1 29/35] perf vendor events: Update skylake metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 30/35] perf vendor events: Update skylakex events/metrics Ian Rogers
2025-03-22 6:33 ` [PATCH v1 31/35] perf vendor events: Update snowridgex events Ian Rogers
2025-03-22 6:34 ` [PATCH v1 32/35] perf vendor events: Update tigerlake metrics Ian Rogers
2025-03-22 6:34 ` [PATCH v1 33/35] perf vendor events: Update westmereep-dp events Ian Rogers
2025-03-22 6:34 ` [PATCH v1 34/35] " Ian Rogers
2025-03-22 6:34 ` [PATCH v1 35/35] " 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=20250322063403.364981-25-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=alexandre.torgue@foss.st.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=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
--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 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.