[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bbbd024c-d2df-47ea-9587-f68e5bc45962@linux.intel.com>
Date: Fri, 27 Sep 2024 14:33:57 -0400
From: "Liang, Kan" <kan.liang@...ux.intel.com>
To: Ian Rogers <irogers@...gle.com>, Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>, Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
Perry Taylor <perry.taylor@...el.com>, Samantha Alt
<samantha.alt@...el.com>, Caleb Biggers <caleb.biggers@...el.com>,
Weilin Wang <weilin.wang@...el.com>, Edward Baker <edward.baker@...el.com>
Subject: Re: [PATCH v4 00/22] Python generated Intel metrics
On 2024-09-26 1:50 p.m., Ian Rogers wrote:
> Generate twenty sets of additional metrics for Intel. Rapl and Idle
> metrics aren't specific to Intel but are placed here for ease and
> convenience. Smi and tsx metrics are added so they can be dropped from
> the per model json files.
Are Smi and tsx metrics the only two metrics who's duplicate metrics in
the json files will be dropped?
It sounds like there will be many duplicate metrics in perf list, right?
Also, is it an attempt to define some architectural metrics for perf?
How do you decide which metrics should be added here?
Thanks,
Kan
> There are four uncore sets of metrics and
> eleven core metrics. Add a CheckPmu function to metric to simplify
> detecting the presence of hybrid PMUs in events. Metrics with
> experimental events are flagged as experimental in their description.
>
> The patches should be applied on top of:
> https://lore.kernel.org/lkml/20240926174101.406874-1-irogers@google.com/
>
> v4. Experimental metric descriptions. Add mesh bandwidth metric. Rebase.
> v3. Swap tsx and CheckPMU patches that were in the wrong order. Some
> minor code cleanup changes. Drop reference to merged fix for
> umasks/occ_sel in PCU events and for cstate metrics.
> v2. Drop the cycles breakdown in favor of having it as a common
> metric, spelling and other improvements suggested by Kan Liang
> <kan.liang@...ux.intel.com>.
>
> Ian Rogers (22):
> perf jevents: Add RAPL metrics for all Intel models
> perf jevents: Add idle metric for Intel models
> perf jevents: Add smi metric group for Intel models
> perf jevents: Add CheckPmu to see if a PMU is in loaded json events
> perf jevents: Mark metrics with experimental events as experimental
> perf jevents: Add tsx metric group for Intel models
> perf jevents: Add br metric group for branch statistics on Intel
> perf jevents: Add software prefetch (swpf) metric group for Intel
> perf jevents: Add ports metric group giving utilization on Intel
> perf jevents: Add L2 metrics for Intel
> perf jevents: Add load store breakdown metrics ldst for Intel
> perf jevents: Add ILP metrics for Intel
> perf jevents: Add context switch metrics for Intel
> perf jevents: Add FPU metrics for Intel
> perf jevents: Add Miss Level Parallelism (MLP) metric for Intel
> perf jevents: Add mem_bw metric for Intel
> perf jevents: Add local/remote "mem" breakdown metrics for Intel
> perf jevents: Add dir breakdown metrics for Intel
> perf jevents: Add C-State metrics from the PCU PMU for Intel
> perf jevents: Add local/remote miss latency metrics for Intel
> perf jevents: Add upi_bw metric for Intel
> perf jevents: Add mesh bandwidth saturation metric for Intel
>
> tools/perf/pmu-events/intel_metrics.py | 1046 +++++++++++++++++++++++-
> tools/perf/pmu-events/metric.py | 52 ++
> 2 files changed, 1095 insertions(+), 3 deletions(-)
>
Powered by blists - more mailing lists