From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "Baker, Edward" <edward.baker@intel.com>,
"Wang, Weilin" <weilin.wang@intel.com>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"xu.yang_2@nxp.com" <xu.yang_2@nxp.com>,
"Biggers, Caleb" <caleb.biggers@intel.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"Taylor, Perry" <perry.taylor@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"irogers@google.com" <irogers@google.com>,
"sandipan.das@amd.com" <sandipan.das@amd.com>,
"james.clark@linaro.org" <james.clark@linaro.org>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"john.g.garry@oracle.com" <john.g.garry@oracle.com>,
"bgray@linux.ibm.com" <bgray@linux.ibm.com>,
"Alt, Samantha" <samantha.alt@intel.com>,
"renyu.zj@linux.alibaba.com" <renyu.zj@linux.alibaba.com>,
"acme@kernel.org" <acme@kernel.org>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>
Subject: Re: [PATCH v6 05/22] perf jevents: Mark metrics with experimental events as experimental
Date: Wed, 17 Sep 2025 18:02:45 +0000 [thread overview]
Message-ID: <ef20fc6501c57d932024ad31323f90165caeae28.camel@intel.com> (raw)
In-Reply-To: <20250904044653.1002362-6-irogers@google.com>
On Wed, 2025-09-03 at 21:46 -0700, Ian Rogers wrote:
> When metrics are made with experimental events it is desirable the
> metric description also carries this information in case of metric
> inaccuracies.
>
> Suggested-by: Perry Taylor <perry.taylor@intel.com>
Does this need a Signed-off-by?
Thanks,
Tom
> ---
> tools/perf/pmu-events/metric.py | 44 +++++++++++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/tools/perf/pmu-events/metric.py b/tools/perf/pmu-events/metric.py
> index 62d1a1e1d458..2029b6e28365 100644
> --- a/tools/perf/pmu-events/metric.py
> +++ b/tools/perf/pmu-events/metric.py
> @@ -10,11 +10,13 @@ from typing import Dict, List, Optional, Set, Tuple, Union
>
> all_pmus = set()
> all_events = set()
> +experimental_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
> + global experimental_events
> all_events = {
> "context\\-switches",
> "cpu\\-cycles",
> @@ -32,6 +34,8 @@ def LoadEvents(directory: str) -> None:
> all_pmus.add(x["Unit"])
> if "EventName" in x:
> all_events.add(x["EventName"])
> + if "Experimental" in x and x["Experimental"] == "1":
> + experimental_events.add(x["EventName"])
> elif "ArchStdEvent" in x:
> all_events.add(x["ArchStdEvent"])
> except json.decoder.JSONDecodeError:
> @@ -61,6 +65,18 @@ def CheckEvent(name: str) -> bool:
> return name in all_events
>
>
> +def IsExperimentalEvent(name: str) -> bool:
> + global experimental_events
> + if ':' in name:
> + # Remove trailing modifier.
> + name = name[:name.find(':')]
> + elif '/' in name:
> + # Name could begin with a PMU or an event, for now assume it is not experimental.
> + return False
> +
> + return name in experimental_events
> +
> +
> class MetricConstraint(Enum):
> GROUPED_EVENTS = 0
> NO_GROUP_EVENTS = 1
> @@ -82,6 +98,10 @@ class Expression:
> """Returns a simplified version of self."""
> raise NotImplementedError()
>
> + def HasExperimentalEvents(self) -> bool:
> + """Are experimental events used in the expression?"""
> + raise NotImplementedError()
> +
> def Equals(self, other) -> bool:
> """Returns true when two expressions are the same."""
> raise NotImplementedError()
> @@ -249,6 +269,9 @@ class Operator(Expression):
>
> return Operator(self.operator, lhs, rhs)
>
> + def HasExperimentalEvents(self) -> bool:
> + return self.lhs.HasExperimentalEvents() or self.rhs.HasExperimentalEvents()
> +
> def Equals(self, other: Expression) -> bool:
> if isinstance(other, Operator):
> return self.operator == other.operator and self.lhs.Equals(
> @@ -297,6 +320,10 @@ class Select(Expression):
>
> return Select(true_val, cond, false_val)
>
> + def HasExperimentalEvents(self) -> bool:
> + return (self.cond.HasExperimentalEvents() or self.true_val.HasExperimentalEvents() or
> + self.false_val.HasExperimentalEvents())
> +
> def Equals(self, other: Expression) -> bool:
> if isinstance(other, Select):
> return self.cond.Equals(other.cond) and self.false_val.Equals(
> @@ -345,6 +372,9 @@ class Function(Expression):
>
> return Function(self.fn, lhs, rhs)
>
> + def HasExperimentalEvents(self) -> bool:
> + return self.lhs.HasExperimentalEvents() or (self.rhs and self.rhs.HasExperimentalEvents())
> +
> def Equals(self, other: Expression) -> bool:
> if isinstance(other, Function):
> result = self.fn == other.fn and self.lhs.Equals(other.lhs)
> @@ -384,6 +414,9 @@ class Event(Expression):
> global all_events
> raise Exception(f"No event {error} in:\n{all_events}")
>
> + def HasExperimentalEvents(self) -> bool:
> + return IsExperimentalEvent(self.name)
> +
> def ToPerfJson(self):
> result = re.sub('/', '@', self.name)
> return result
> @@ -416,6 +449,9 @@ class MetricRef(Expression):
> def Simplify(self) -> Expression:
> return self
>
> + def HasExperimentalEvents(self) -> bool:
> + return False
> +
> def Equals(self, other: Expression) -> bool:
> return isinstance(other, MetricRef) and self.name == other.name
>
> @@ -443,6 +479,9 @@ class Constant(Expression):
> def Simplify(self) -> Expression:
> return self
>
> + def HasExperimentalEvents(self) -> bool:
> + return False
> +
> def Equals(self, other: Expression) -> bool:
> return isinstance(other, Constant) and self.value == other.value
>
> @@ -465,6 +504,9 @@ class Literal(Expression):
> def Simplify(self) -> Expression:
> return self
>
> + def HasExperimentalEvents(self) -> bool:
> + return False
> +
> def Equals(self, other: Expression) -> bool:
> return isinstance(other, Literal) and self.value == other.value
>
> @@ -527,6 +569,8 @@ class Metric:
> self.name = name
> self.description = description
> self.expr = expr.Simplify()
> + if self.expr.HasExperimentalEvents():
> + self.description += " (metric should be considered experimental as it contains experimental events)."
> # Workraound valid_only_metric hiding certain metrics based on unit.
> scale_unit = scale_unit.replace('/sec', ' per sec')
> if scale_unit[0].isdigit():
next prev parent reply other threads:[~2025-09-17 18:02 UTC|newest]
Thread overview: 27+ 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 ` [PATCH v6 03/22] perf jevents: Add CheckPmu to see if a PMU is in loaded json events Ian Rogers
2025-09-04 4:46 ` [PATCH v6 04/22] perf jevents: Add smi metric group for Intel models Ian Rogers
2025-09-04 4:46 ` [PATCH v6 05/22] perf jevents: Mark metrics with experimental events as experimental Ian Rogers
2025-09-17 18:02 ` Falcon, Thomas [this message]
2025-09-17 20:49 ` 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
2025-09-19 15:31 ` [PATCH v6 00/22] Python generated Intel metrics Falcon, Thomas
2025-09-20 12:54 ` 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=ef20fc6501c57d932024ad31323f90165caeae28.camel@intel.com \
--to=thomas.falcon@intel.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=irogers@google.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=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).