From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "Biggers, Caleb" <caleb.biggers@intel.com>,
"irogers@google.com" <irogers@google.com>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>
Cc: "alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"mpetlan@redhat.com" <mpetlan@redhat.com>,
"Taylor, Perry" <perry.taylor@intel.com>,
"Hunter, Adrian" <adrian.hunter@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>,
"manivannan.sadhasivam@linaro.org"
<manivannan.sadhasivam@linaro.org>,
"Alt, Samantha" <samantha.alt@intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"Wang, Weilin" <weilin.wang@intel.com>,
"Baker, Edward" <edward.baker@intel.com>,
"acme@kernel.org" <acme@kernel.org>,
"afaerber@suse.de" <afaerber@suse.de>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>
Subject: Re: [PATCH v2 00/23] Intel vendor events and TMA 5.01 metrics
Date: Fri, 17 Jan 2025 20:30:12 +0000 [thread overview]
Message-ID: <b5821a8375372fddd16ee6b53bf4cd218bdf9a8b.camel@intel.com> (raw)
In-Reply-To: <CAP-5=fWzoxFDqEvVzTWoj0RRTDCuHxmENAyWqshQu2NQZYoJZg@mail.gmail.com>
On Fri, 2025-01-17 at 11:43 -0800, Ian Rogers wrote:
> On Fri, Jan 17, 2025 at 11:10 AM Liang, Kan
> <kan.liang@linux.intel.com> wrote:
> >
> >
> >
> > On 2025-01-17 11:03 a.m., Liang, Kan wrote:
> > >
> > >
> > > On 2025-01-16 1:43 a.m., Ian Rogers wrote:
> > > > Update the Intel vendor events to the latest.
> > > > Update the metrics to TMA 5.01.
> > > > Add Arrowlake and Clearwaterforest support.
> > > > Add metrics for LNL and GNR.
> > > > Address IIO uncore issue spotted on EMR, GRR, GNR, SPR and SRF.
> > > >
> > > > The perf json was generated using the script:
> > > > https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
> > > > with the generated json being in:
> > > > https://github.com/intel/perfmon/tree/main/scripts/perf
> > > >
> > > > Thanks to Perry Taylor <perry.taylor@intel.com>, Caleb Biggers
> > > > <caleb.biggers@intel.com>, Edward Baker
> > > > <edward.baker@intel.com> and
> > > > Weilin Wang <weilin.wang@intel.com> for helping get this patch
> > > > series
> > > > together.
> > > >
> > > > v2: Fix hybrid and Co-authored-by tag issues reported by
> > > > Arnaldo. Updates to Lunarlake and Meteorlake events.
> > > > Addition of
> > > > Clearwaterforest.
> > >
> > > Thanks Ian!
> > >
> > > Acked-by: Kan Liang <kan.liang@linux.intel.com>
> > >
> >
> > Thanks Thomas to do more tests for the series.
> >
> > There is an issue for the FP_ARITH* related metrics on hybrid
> > platforms.
> > I have to take the acked-by back. Sorry for the noise.
> >
> > Here is the issue on ADL and ARL.
> >
> > $ sudo ./perf stat -M tma_info_inst_mix_iparith -a sleep 1
> > Cannot resolve IDs for tma_info_inst_mix_iparith: INST_RETIRED.ANY
> > /
> > (FP_ARITH_INST_RETIRED.SCALAR + FP_ARITH_INST_RETIRED.VECTOR)
> >
> >
> > The patch set add the tma_info_inst_mix_iparith for cpu_atom.
> >
> > + {
> > + "BriefDescription": "Instructions per FP Arithmetic
> > instruction
> > (lower number means higher occurrence rate)",
> > + "MetricExpr": "INST_RETIRED.ANY /
> > (FP_ARITH_INST_RETIRED.SCALAR
> > + FP_ARITH_INST_RETIRED.VECTOR)",
> > + "MetricGroup": "Flops;InsType;Inst_Metric",
> > + "MetricName": "tma_info_inst_mix_iparith",
> > + "MetricThreshold": "tma_info_inst_mix_iparith < 10",
> > + "PublicDescription": "Instructions per FP Arithmetic
> > instruction (lower number means higher occurrence rate). Values < 1
> > are
> > possible due to intentional FMA double counting. Approximated prior
> > to BDW",
> > + "Unit": "cpu_atom"
> > + },
> >
> > However, the FP_ARITH_INST_RETIRED.SCALAR and
> > FP_ARITH_INST_RETIRED.VECTOR event are only available for cpu_core.
> >
> > sudo ./perf stat -e FP_ARITH_INST_RETIRED.SCALAR -a sleep 1
> >
> > Performance counter stats for 'system wide':
> >
> > 0 cpu_core/FP_ARITH_INST_RETIRED.SCALAR/
> >
> > There should be no such metric for cpu_atom.
>
> Thanks Thomas and Kan!
>
> The metric came from here:
> https://github.com/intel/perfmon/blob/main/ADL/metrics/perf/alderlake_metrics_goldencove_core_perf.json#L1243
> and the event being in the cpu_core will explain why it passed the
> sanity check that all events are in the event json.
>
> I believe Caleb can address the issue. I think all the events need
> PMU
> prefixes as happened previously here:
> https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py#L1535
>
> A few more kinks to resolve in the new TMA release process, thanks
> for
> the testing!
> Ian
Thanks, I'm also seeing some weirdness in the perf all metrics and
metricsgroups tests with verbose output:
.../perf-tools-next/tools/perf# ./perf test 95
95: perf all metrics test :
Skip
.../perf-tools-next/tools/perf# ./perf test 95 -vvv
95: perf all metrics test:
--- start ---
test child forked, pid 135502
Testing tma_core_bound
...
Testing tma_fp_scalar
FP issues
Cannot resolve IDs for tma_fp_scalar: FP_ARITH_INST_RETIRED.SCALAR /
(tma_retiring arch bench Build builtin-annotate.c builtin-annotate.o
builtin-bench.c builtin-bench.o builtin-buildid-cache.c builtin-
buildid-cache.o builtin-buildid-list.c builtin-buildid-list.o builtin-
c2c.c builtin-c2c.o builtin-check.c builtin-check.o builtin-config.c
builtin-config.o builtin-daemon.c builtin-daemon.o builtin-data.c
builtin-data.o builtin-diff.c builtin-diff.o builtin-evlist.c builtin-
evlist.o builtin-ftrace.c builtin-ftrace.o builtin.h builtin-help.c
builtin-help.o builtin-inject.c builtin-inject.o builtin-kallsyms.c
builtin-kallsyms.o builtin-kmem.c builtin-kmem.o builtin-kvm.c builtin-
kvm.o builtin-kwork.c builtin-kwork.o builtin-list.c builtin-list.o
builtin-lock.c builtin-lock.o builtin-mem.c builtin-mem.o builtin-
probe.c builtin-probe.o builtin-record.c builtin-record.o builtin-
report.c builtin-report.o builtin-sched.c builtin-sched.o builtin-
script.c builtin-script.o builtin-stat.c builtin-stat.o builtin-
timechart.c builtin-timechart.o builtin-top.c builtin-top.o builtin-
trace.c builtin-trace.o builtin-version.c builtin-version.o check-
header_ignore_hunks check-headers.sh check-headers.sh.shellcheck_log
command-list.txt common-cmds.h CREDITS design.txt dlfilters
Documentation FEATURE-DUMP include jvmti libapi libbpf libperf libperf-
bench.a libperf-jvmti.so libperf-test.a libperf-ui.a libperf-util.a
libpmu-events.a libsubcmd libsymbol Makefile Makefile.config
Makefile.perf MANIFEST perf perf-archive perf-archive.sh perf-
archive.sh.shellcheck_log perf-bench-in.o perf.c perf-completion.sh
perf-completion.sh.shellcheck_log perf.h perf-in.o perf-iostat perf-
iostat.sh perf-iostat.sh.shellcheck_log perf.o perf-read-vdso32 perf-
read-vdso.c perf-sys.h perf-test-in.o perf-ui-in.o perf-util-in.o PERF-
VERSION-FILE pmu-events python python_ext_build scripts tests trace ui
util tma_info_thread_slots)
...
---- end(-2) ----
95: perf all metrics test :
Skip
The * is getting replaced with the files in my working directory, which
is tools/perf, but only when running 'perf test', running 'perf stat'
just prints the error normally:
.../perf-tools-next/tools/perf# ./perf stat -M tma_fp_scalar sleep 1
Cannot resolve IDs for tma_fp_scalar: FP_ARITH_INST_RETIRED.SCALAR /
(tma_retiring * tma_info_thread_slots)
Tom
prev parent reply other threads:[~2025-01-17 20:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 6:43 [PATCH v2 00/23] Intel vendor events and TMA 5.01 metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 01/23] perf vendor events: Update Alderlake events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 02/23] perf vendor events: Update AlderlakeN events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 03/23] perf vendor events: Add Arrowlake events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 04/23] perf vendor events: Update Broadwell events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 05/23] perf vendor events: Update BroadwellDE events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 06/23] perf vendor events: Update BroadwellX events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 07/23] perf vendor events: Update CascadelakeX events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 08/23] perf vendor events: Add Clearwaterforest events Ian Rogers
2025-01-16 6:43 ` [PATCH v2 09/23] perf vendor events: Update EmeraldRapids events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 10/23] perf vendor events: Update GrandRidge events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 11/23] perf vendor events: Update/add Graniterapids events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 12/23] perf vendor events: Update Haswell events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 13/23] perf vendor events: Update HaswellX events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 14/23] perf vendor events: Update Icelake events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 15/23] perf vendor events: Update IcelakeX events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 16/23] perf vendor events: Update/add Lunarlake events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 17/23] perf vendor events: Update Meteorlake events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 18/23] perf vendor events: Update Rocketlake events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 19/23] perf vendor events: Update Sapphirerapids events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 20/23] perf vendor events: Update Sierraforest events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 21/23] perf vendor events: Update Skylake metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 22/23] perf vendor events: Update SkylakeX events/metrics Ian Rogers
2025-01-16 6:43 ` [PATCH v2 23/23] perf vendor events: Update Tigerlake events/metrics Ian Rogers
2025-01-17 16:03 ` [PATCH v2 00/23] Intel vendor events and TMA 5.01 metrics Liang, Kan
2025-01-17 19:10 ` Liang, Kan
2025-01-17 19:43 ` Ian Rogers
2025-01-17 20:30 ` Falcon, Thomas [this message]
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=b5821a8375372fddd16ee6b53bf4cd218bdf9a8b.camel@intel.com \
--to=thomas.falcon@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=irogers@google.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=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@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