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 v3 33/35] perf vendor events: Update westmereep-dp events
Date: Tue, 25 Mar 2025 17:04:31 -0700 [thread overview]
Message-ID: <20250326000434.83325-34-irogers@google.com> (raw)
In-Reply-To: <20250326000434.83325-1-irogers@google.com>
Update event topic moving other topic events to cache and virtual
memory.
Signed-off-by: Ian Rogers <irogers@google.com>
---
.../arch/x86/westmereep-dp/cache.json | 32 +++++++++++++++
.../arch/x86/westmereep-dp/other.json | 40 -------------------
.../x86/westmereep-dp/virtual-memory.json | 8 ++++
3 files changed, 40 insertions(+), 40 deletions(-)
diff --git a/tools/perf/pmu-events/arch/x86/westmereep-dp/cache.json b/tools/perf/pmu-events/arch/x86/westmereep-dp/cache.json
index 30845c7dbf08..f6f95f3ff301 100644
--- a/tools/perf/pmu-events/arch/x86/westmereep-dp/cache.json
+++ b/tools/perf/pmu-events/arch/x86/westmereep-dp/cache.json
@@ -119,6 +119,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/westmereep-dp/other.json b/tools/perf/pmu-events/arch/x86/westmereep-dp/other.json
index bcf5bcf637c0..c0cf8bae8074 100644
--- a/tools/perf/pmu-events/arch/x86/westmereep-dp/other.json
+++ b/tools/perf/pmu-events/arch/x86/westmereep-dp/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": "Loads that partially overlap an earlier store",
"Counter": "0,1,2,3",
diff --git a/tools/perf/pmu-events/arch/x86/westmereep-dp/virtual-memory.json b/tools/perf/pmu-events/arch/x86/westmereep-dp/virtual-memory.json
index 53d7f76325a3..84c920637b12 100644
--- a/tools/perf/pmu-events/arch/x86/westmereep-dp/virtual-memory.json
+++ b/tools/perf/pmu-events/arch/x86/westmereep-dp/virtual-memory.json
@@ -152,6 +152,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-26 0:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 0:03 [PATCH v3 00/35] GNR retirement latencies, topic and metric updates Ian Rogers
2025-03-26 0:03 ` [PATCH v3 01/35] perf vendor events: Update alderlake events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 02/35] perf vendor events: Update AlderlakeN events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 03/35] perf vendor events: Update arrowlake events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 04/35] perf vendor events: Update bonnell events Ian Rogers
2025-03-26 0:04 ` [PATCH v3 05/35] perf vendor events: Update broadwell metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 06/35] perf vendor events: Update broadwellde metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 07/35] perf vendor events: Update broadwellx metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 08/35] perf vendor events: Update cascadelakex events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 09/35] perf vendor events: Update clearwaterforest events Ian Rogers
2025-03-26 0:04 ` [PATCH v3 10/35] perf vendor events: Update elkhartlake events Ian Rogers
2025-03-26 0:04 ` [PATCH v3 11/35] perf vendor events: Update emeraldrapids events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 12/35] perf vendor events: Update grandridge events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 13/35] perf vendor events: Add graniterapids retirement latencies Ian Rogers
2025-03-26 0:04 ` [PATCH v3 14/35] perf vendor events: Update haswell metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 15/35] perf vendor events: Update haswellx metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 16/35] perf vendor events: Update icelake events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 17/35] perf vendor events: Update icelakex events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 18/35] perf vendor events: Update ivybridge metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 19/35] perf vendor events: Update ivytown metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 20/35] perf vendor events: Update jaketown metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 21/35] perf vendor events: Update lunarlake events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 22/35] perf vendor events: Update meteorlake events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 23/35] perf vendor events: Update nehalemep events Ian Rogers
2025-03-26 0:04 ` [PATCH v3 24/35] perf vendor events: Update nehalemex events Ian Rogers
2025-03-26 0:04 ` [PATCH v3 25/35] perf vendor events: Update rocketlake events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 26/35] perf vendor events: Update sandybridge metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 27/35] perf vendor events: Update sapphirerapids events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 28/35] perf vendor events: Update sierraforest events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 29/35] perf vendor events: Update skylake metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 30/35] perf vendor events: Update skylakex events/metrics Ian Rogers
2025-03-26 0:04 ` [PATCH v3 31/35] perf vendor events: Update snowridgex events Ian Rogers
2025-03-26 0:04 ` [PATCH v3 32/35] perf vendor events: Update tigerlake metrics Ian Rogers
2025-03-26 0:04 ` Ian Rogers [this message]
2025-03-26 0:04 ` [PATCH v3 34/35] perf vendor events: Update westmereep-dp events Ian Rogers
2025-03-26 0:04 ` [PATCH v3 35/35] " Ian Rogers
2025-03-26 22:10 ` [PATCH v3 00/35] GNR retirement latencies, topic and metric updates Falcon, Thomas
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=20250326000434.83325-34-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox