From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "irogers@google.com" <irogers@google.com>
Cc: "alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"Biggers, Caleb" <caleb.biggers@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>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"Baker, Edward" <edward.baker@intel.com>,
"Alt, Samantha" <samantha.alt@intel.com>,
"Wang, Weilin" <weilin.wang@intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"acme@kernel.org" <acme@kernel.org>,
"manivannan.sadhasivam@linaro.org"
<manivannan.sadhasivam@linaro.org>,
"afaerber@suse.de" <afaerber@suse.de>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>
Subject: Re: [PATCH v5 00/24] Intel vendor events and TMA 5.01 metrics
Date: Thu, 6 Feb 2025 20:33:09 +0000 [thread overview]
Message-ID: <cfea58d7357fc974613cbf65197b1069cbd4e749.camel@intel.com> (raw)
In-Reply-To: <CAP-5=fUjx3PTHfjgkam9Q0xE+TrYx+FSzF8wUscbD9X36gJ1Tg@mail.gmail.com>
On Wed, 2025-02-05 at 12:47 -0800, Ian Rogers wrote:
> On Wed, Feb 5, 2025 at 11:44 AM Falcon, Thomas
> <thomas.falcon@intel.com> wrote:
> >
> > On Wed, 2025-02-05 at 09:31 -0800, 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>,
> > > Weilin Wang <weilin.wang@intel.com>, Kan Liang
> > > <kan.liang@linux.intel.com> and Thomas Falcon
> > > <thomas.falcon@intel.com> for helping get this patch series
> > > together.
> > >
> > > v5: Remove Valkyrie metrics mistakenly added on atom. Ensure
> > > "perf
> > > all
> > > metrics test" doesn't skip for missing events.
> > > v4: Fix TSC events on hybrid mistakenly specifying the core PMU
> > > inhibiting the use of the msr PMU.
> > > v3: Fixes for hybrid metrics that were missing PMU. Update to the
> > > latest events.
> > > v2: Fix hybrid and Co-authored-by tag issues reported by
> > > Arnaldo. Updates to Lunarlake and Meteorlake events. Addition
> > > of
> > > Clearwaterforest.
> > >
> >
> > Thanks, I'm seeing some errors during the perf all metrics test:
> >
> > Metric 'tma_info_system_cpus_utilized' not printed in:
> > event syntax error: '{cpu_core/TSC,metric-
> > id=cpu_core!3TSC!3/,cpu_core/CPU_CL..'
> > \___ Bad event or PMU
> >
> > Unable to find PMU or event on a PMU of 'cpu_core'
> >
> > event syntax error: '{cpu_core/TSC,metric-
> > id=cpu_core!3TSC!3/,cpu_core/CPU_CL..'
> > \___ unknown term 'TSC' for pmu
> > 'cpu_core'
> >
> > valid terms:
> > event,pc,edge,offcore_rsp,ldlat,inv,umask,frontend,cmask,config,con
> > fig1
> > ,config2,config3,name,period,percore,metric-id
> >
> > event syntax error: '{cpu_core/TSC,metric-
> > id=cpu_core!3TSC!3/,cpu_core/CPU_CL..'
> > \___ unknown term 'TSC' for pmu
> > 'cpu_core'
> >
> > valid terms:
> > event,pc,edge,offcore_rsp,ldlat,inv,umask,frontend,cmask,config,con
> > fig1
> > ,config2,config3,name,period,percore,metric-id
> >
> > There are all some errors like this,
> >
> > Testing tma_cisc
> > Metric contains missing events
> > Cannot resolve IDs for tma_cisc: cpu_atom@TOPDOWN_FE_BOUND.CISC@ /
> > (5 *
> > cpu_atom@CPU_CLK_UNHALTED.CORE@)
> >
>
> Thanks, I forgot to reapply the TSC fix. You can do it with
> $ find tools/perf/pmu-events/arch/x86 -type f -exec sed -i
> 's/cpu_core@TSC@/TSC/g' {} \;
> I can't eyeball this later missing events problem. What model type
> does it happen on?
Thanks, I was testing on Alder Lake, which seems ok now other than the
"Cannot resolve IDs..." errors after your TSC change. I am seeing
similar errors on an Arrow Lake though as well as these errors:
Metric 'C7_Pkg_Residency' not printed in:
event syntax error: '{cstate_pkg/c7-residency,metric-
id=cstate_pkg!3c7!1resid..'
\___ Bad event or PMU
Unable to find PMU or event on a PMU of 'cstate_pkg'
event syntax error: '{cstate_pkg/c7-residency,metric-
id=cstate_pkg!3c7!1resid..'
\___ unknown term 'c7-residency' for
pmu 'cstate_pkg'
valid terms:
event,config,config1,config2,config3,name,period,percore,metric-id
event syntax error: '{cstate_pkg/c7-residency,metric-
id=cstate_pkg!3c7!1resid..'
\___ unknown term 'c7-residency' for
pmu 'cstate_pkg'
valid terms:
event,config,config1,config2,config3,name,period,percore,metric-id
Testing C8_Pkg_Residency
Testing C9_Pkg_Residency
Metric 'C9_Pkg_Residency' not printed in:
event syntax error: '{cstate_pkg/c9-residency,metric-
id=cstate_pkg!3c9!1resid..'
\___ Bad event or PMU
Unable to find PMU or event on a PMU of 'cstate_pkg'
event syntax error: '{cstate_pkg/c9-residency,metric-
id=cstate_pkg!3c9!1resid..'
\___ unknown term 'c9-residency' for
pmu 'cstate_pkg'
valid terms:
event,config,config1,config2,config3,name,period,percore,metric-id
event syntax error: '{cstate_pkg/c9-residency,metric-
id=cstate_pkg!3c9!1resid..'
\___ unknown term 'c9-residency' for
pmu 'cstate_pkg'
valid terms:
event,config,config1,config2,config3,name,period,percore,metric-id
Testing tma_info_core_epc
Testing tma_info_system_core_frequency
Testing tma_info_system_power
Testing tma_info_system_turbo_utilization
Testing tma_info_inst_mix_ipswpf
Testing tma_info_memory_prefetches_useless_hwpf
Testing tma_info_thread_ipc
Testing tma_heavy_operations
Testing tma_light_operations
Testing UNCORE_FREQ
Metric 'UNCORE_FREQ' not printed in:
event syntax error: '{UNC_CLOCK.SOCKET/metric-
id=UNC_CLOCK.SOCKET/}:W,duratio..'
\___ Bad event or PMU
Unable to find PMU or event on a PMU of 'UNC_CLOCK.SOCKET'
Testing tma_info_system_socket_clks
Metric 'tma_info_system_socket_clks' not printed in:
event syntax error: '{UNC_CLOCK.SOCKET/metric-id=UNC_CLOCK.SOCKET/}:W'
\___ Bad event or PMU
Unable to find PMU or event on a PMU of 'UNC_CLOCK.SOCKET'
I submitted a PR to perfmon for the c7/c9-residency errors.
Tom
> Thanks,
> Ian
>
prev parent reply other threads:[~2025-02-06 20:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 17:31 [PATCH v5 00/24] Intel vendor events and TMA 5.01 metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 01/24] perf vendor events: Update Alderlake events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 02/24] perf vendor events: Update AlderlakeN events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 03/24] perf vendor events: Add Arrowlake events/metrics Ian Rogers
2025-02-05 19:08 ` Liang, Kan
2025-02-05 17:31 ` [PATCH v5 04/24] perf vendor events: Update Broadwell events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 05/24] perf vendor events: Update BroadwellDE events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 06/24] perf vendor events: Update BroadwellX events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 07/24] perf vendor events: Update CascadelakeX events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 08/24] perf vendor events: Add Clearwaterforest events Ian Rogers
2025-02-05 17:31 ` [PATCH v5 09/24] perf vendor events: Update EmeraldRapids events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 10/24] perf vendor events: Update GrandRidge events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 11/24] perf vendor events: Update/add Graniterapids events/metrics Ian Rogers
2025-02-05 19:11 ` Liang, Kan
2025-02-05 20:23 ` Ian Rogers
2025-02-05 21:10 ` Liang, Kan
2025-02-05 21:33 ` Ian Rogers
2025-02-06 14:32 ` Liang, Kan
2025-02-06 16:40 ` Ian Rogers
2025-02-06 17:11 ` Liang, Kan
[not found] ` <CAP-5=fWQj01O3WmGLoAf6O_uEeMHpOUqVWvHi3nW_kGj4VtZWg@mail.gmail.com>
2025-02-06 18:53 ` Liang, Kan
2025-02-06 18:59 ` Liang, Kan
2025-02-06 19:05 ` Ian Rogers
2025-02-06 19:53 ` Liang, Kan
2025-02-07 17:39 ` Ian Rogers
2025-02-05 17:31 ` [PATCH v5 12/24] perf vendor events: Update Haswell events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 13/24] perf vendor events: Update HaswellX events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 14/24] perf vendor events: Update Icelake events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 15/24] perf vendor events: Update IcelakeX events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 16/24] perf vendor events: Update/add Lunarlake events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 17/24] perf vendor events: Update Meteorlake events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 18/24] perf vendor events: Update Rocketlake events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 19/24] perf vendor events: Update Sapphirerapids events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 20/24] perf vendor events: Update Sierraforest events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 21/24] perf vendor events: Update Skylake metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 22/24] perf vendor events: Update SkylakeX events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 23/24] perf vendor events: Update Tigerlake events/metrics Ian Rogers
2025-02-05 17:31 ` [PATCH v5 24/24] perf test stat_all_metrics: Ensure missing events fail test Ian Rogers
2025-02-05 19:44 ` [PATCH v5 00/24] Intel vendor events and TMA 5.01 metrics Falcon, Thomas
2025-02-05 20:47 ` Ian Rogers
2025-02-06 20:33 ` 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=cfea58d7357fc974613cbf65197b1069cbd4e749.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;
as well as URLs for NNTP newsgroup(s).