From: Trevor Allison <tallison@redhat.com>
To: linux-perf-users@vger.kernel.org, acme@kernel.org
Cc: peterz@infradead.org, mingo@redhat.com, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, tallison@redhat.com, mpetlan@redhat.org
Subject: [PATCH] perf pmu: fix unit listing for SPR uncore event
Date: Wed, 26 Nov 2025 11:59:57 -0500 [thread overview]
Message-ID: <20251126165957.96312-1-tallison@redhat.com> (raw)
Fix issue where certain SPR uncore "M3UPI" events were listed as
just "UPI" in the json, causing them not to be found.
Fixes 54f5de6f2998c
Signed-off-by: Trevor Allison <tallison@redhat.com>
---
.../arch/x86/sapphirerapids/uncore-interconnect.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/pmu-events/arch/x86/sapphirerapids/uncore-interconnect.json b/tools/perf/pmu-events/arch/x86/sapphirerapids/uncore-interconnect.json
index 8b1ae9540066..64eb0d02af57 100644
--- a/tools/perf/pmu-events/arch/x86/sapphirerapids/uncore-interconnect.json
+++ b/tools/perf/pmu-events/arch/x86/sapphirerapids/uncore-interconnect.json
@@ -6640,7 +6640,7 @@
"PerPkg": "1",
"PublicDescription": "Valid Flits Received : All Data : Shows legal flit time (hides impact of L0p and L0c).",
"UMask": "0xf",
- "Unit": "UPI"
+ "Unit": "M3UPI"
},
{
"BriefDescription": "Null FLITs received from any slot",
@@ -7146,7 +7146,7 @@
"PerPkg": "1",
"PublicDescription": "Valid Flits Sent : All Data : Counts number of data flits across this UPI link.",
"UMask": "0xf",
- "Unit": "UPI"
+ "Unit": "M3UPI"
},
{
"BriefDescription": "Valid Flits Sent : All LLCRD Not Empty",
--
2.50.1 (Apple Git-155)
reply other threads:[~2025-11-26 17:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251126165957.96312-1-tallison@redhat.com \
--to=tallison@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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).