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 09/35] perf vendor events: Update clearwaterforest events
Date: Tue, 25 Mar 2025 17:04:07 -0700 [thread overview]
Message-ID: <20250326000434.83325-10-irogers@google.com> (raw)
In-Reply-To: <20250326000434.83325-1-irogers@google.com>
Update event topic of OCR.DEMAND_DATA_RD.ANY_RESPONSE and
OCR.DEMAND_RFO.ANY_RESPONSE to be cache.
Signed-off-by: Ian Rogers <irogers@google.com>
---
.../arch/x86/clearwaterforest/cache.json | 20 +++++++++++++++++
.../arch/x86/clearwaterforest/other.json | 22 -------------------
2 files changed, 20 insertions(+), 22 deletions(-)
delete mode 100644 tools/perf/pmu-events/arch/x86/clearwaterforest/other.json
diff --git a/tools/perf/pmu-events/arch/x86/clearwaterforest/cache.json b/tools/perf/pmu-events/arch/x86/clearwaterforest/cache.json
index 875361b30f1d..17f8bfba56bc 100644
--- a/tools/perf/pmu-events/arch/x86/clearwaterforest/cache.json
+++ b/tools/perf/pmu-events/arch/x86/clearwaterforest/cache.json
@@ -140,5 +140,25 @@
"EventName": "MEM_UOPS_RETIRED.STORE_LATENCY",
"SampleAfterValue": "1000003",
"UMask": "0x6"
+ },
+ {
+ "BriefDescription": "Counts demand data reads that have any type of response.",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0xB7",
+ "EventName": "OCR.DEMAND_DATA_RD.ANY_RESPONSE",
+ "MSRIndex": "0x1a6,0x1a7",
+ "MSRValue": "0x10001",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1"
+ },
+ {
+ "BriefDescription": "Counts demand read for ownership (RFO) requests and software prefetches for exclusive ownership (PREFETCHW) that have any type of response.",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0xB7",
+ "EventName": "OCR.DEMAND_RFO.ANY_RESPONSE",
+ "MSRIndex": "0x1a6,0x1a7",
+ "MSRValue": "0x10002",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1"
}
]
diff --git a/tools/perf/pmu-events/arch/x86/clearwaterforest/other.json b/tools/perf/pmu-events/arch/x86/clearwaterforest/other.json
deleted file mode 100644
index 80454e497f83..000000000000
--- a/tools/perf/pmu-events/arch/x86/clearwaterforest/other.json
+++ /dev/null
@@ -1,22 +0,0 @@
-[
- {
- "BriefDescription": "Counts demand data reads that have any type of response.",
- "Counter": "0,1,2,3,4,5,6,7",
- "EventCode": "0xB7",
- "EventName": "OCR.DEMAND_DATA_RD.ANY_RESPONSE",
- "MSRIndex": "0x1a6,0x1a7",
- "MSRValue": "0x10001",
- "SampleAfterValue": "100003",
- "UMask": "0x1"
- },
- {
- "BriefDescription": "Counts demand read for ownership (RFO) requests and software prefetches for exclusive ownership (PREFETCHW) that have any type of response.",
- "Counter": "0,1,2,3,4,5,6,7",
- "EventCode": "0xB7",
- "EventName": "OCR.DEMAND_RFO.ANY_RESPONSE",
- "MSRIndex": "0x1a6,0x1a7",
- "MSRValue": "0x10002",
- "SampleAfterValue": "100003",
- "UMask": "0x1"
- }
-]
--
2.49.0.395.g12beb8f557-goog
next prev parent reply other threads:[~2025-03-26 0:06 UTC|newest]
Thread overview: 38+ 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 ` Ian Rogers [this message]
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 ` [PATCH v3 33/35] perf vendor events: Update westmereep-dp events Ian Rogers
2025-03-26 0:04 ` [PATCH v3 34/35] " 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
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 17:52 Ian Rogers
2025-03-25 17:52 ` [PATCH v3 09/35] perf vendor events: Update clearwaterforest events 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=20250326000434.83325-10-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