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>,
James Clark <james.clark@linaro.org>,
Xu Yang <xu.yang_2@nxp.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
John Garry <john.g.garry@oracle.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Sandipan Das <sandipan.das@amd.com>,
Benjamin Gray <bgray@linux.ibm.com>,
Perry Taylor <perry.taylor@intel.com>,
Samantha Alt <samantha.alt@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>,
Weilin Wang <weilin.wang@intel.com>,
Edward Baker <edward.baker@intel.com>,
Thomas Falcon <thomas.falcon@intel.com>
Subject: [PATCH v6 03/22] perf jevents: Add CheckPmu to see if a PMU is in loaded json events
Date: Wed, 3 Sep 2025 21:46:34 -0700 [thread overview]
Message-ID: <20250904044653.1002362-4-irogers@google.com> (raw)
In-Reply-To: <20250904044653.1002362-1-irogers@google.com>
CheckPmu can be used to determine if hybrid events are present,
allowing for hybrid conditional metrics/events/pmus to be premised on
the json files rather than hard coded tables.
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/pmu-events/metric.py | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tools/perf/pmu-events/metric.py b/tools/perf/pmu-events/metric.py
index e33e163b2815..62d1a1e1d458 100644
--- a/tools/perf/pmu-events/metric.py
+++ b/tools/perf/pmu-events/metric.py
@@ -8,10 +8,12 @@ import re
from enum import Enum
from typing import Dict, List, Optional, Set, Tuple, Union
+all_pmus = set()
all_events = set()
def LoadEvents(directory: str) -> None:
"""Populate a global set of all known events for the purpose of validating Event names"""
+ global all_pmus
global all_events
all_events = {
"context\\-switches",
@@ -26,6 +28,8 @@ def LoadEvents(directory: str) -> None:
if filename.endswith(".json"):
try:
for x in json.load(open(f"{directory}/{filename}")):
+ if "Unit" in x:
+ all_pmus.add(x["Unit"])
if "EventName" in x:
all_events.add(x["EventName"])
elif "ArchStdEvent" in x:
@@ -36,6 +40,10 @@ def LoadEvents(directory: str) -> None:
pass
+def CheckPmu(name: str) -> bool:
+ return name in all_pmus
+
+
def CheckEvent(name: str) -> bool:
"""Check the event name exists in the set of all loaded events"""
global all_events
--
2.51.0.338.gd7d06c2dae-goog
next prev parent reply other threads:[~2025-09-04 4:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 4:46 [PATCH v6 00/22] Python generated Intel metrics Ian Rogers
2025-09-04 4:46 ` [PATCH v6 01/22] perf jevents: Add RAPL metrics for all Intel models Ian Rogers
2025-09-04 4:46 ` [PATCH v6 02/22] perf jevents: Add idle metric for " Ian Rogers
2025-09-04 4:46 ` Ian Rogers [this message]
2025-09-04 4:46 ` [PATCH v6 04/22] perf jevents: Add smi metric group " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 05/22] perf jevents: Mark metrics with experimental events as experimental Ian Rogers
2025-09-04 4:46 ` [PATCH v6 06/22] perf jevents: Add tsx metric group for Intel models Ian Rogers
2025-09-04 4:46 ` [PATCH v6 07/22] perf jevents: Add br metric group for branch statistics on Intel Ian Rogers
2025-09-04 4:46 ` [PATCH v6 08/22] perf jevents: Add software prefetch (swpf) metric group for Intel Ian Rogers
2025-09-04 4:46 ` [PATCH v6 09/22] perf jevents: Add ports metric group giving utilization on Intel Ian Rogers
2025-09-04 4:46 ` [PATCH v6 10/22] perf jevents: Add L2 metrics for Intel Ian Rogers
2025-09-04 4:46 ` [PATCH v6 11/22] perf jevents: Add load store breakdown metrics ldst " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 12/22] perf jevents: Add ILP metrics " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 13/22] perf jevents: Add context switch " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 14/22] perf jevents: Add FPU " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 15/22] perf jevents: Add Miss Level Parallelism (MLP) metric " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 16/22] perf jevents: Add mem_bw " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 17/22] perf jevents: Add local/remote "mem" breakdown metrics " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 18/22] perf jevents: Add dir " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 19/22] perf jevents: Add C-State metrics from the PCU PMU " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 20/22] perf jevents: Add local/remote miss latency metrics " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 21/22] perf jevents: Add upi_bw metric " Ian Rogers
2025-09-04 4:46 ` [PATCH v6 22/22] perf jevents: Add mesh bandwidth saturation " 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=20250904044653.1002362-4-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bgray@linux.ibm.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=samantha.alt@intel.com \
--cc=sandipan.das@amd.com \
--cc=thomas.falcon@intel.com \
--cc=weilin.wang@intel.com \
--cc=xu.yang_2@nxp.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;
as well as URLs for NNTP newsgroup(s).