From: Namhyung Kim <namhyung@kernel.org>
To: "Falcon, Thomas" <thomas.falcon@intel.com>
Cc: "linux-actions@lists.infradead.org"
<linux-actions@lists.infradead.org>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"Biggers, Caleb" <caleb.biggers@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>,
"irogers@google.com" <irogers@google.com>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"Wang, Weilin" <weilin.wang@intel.com>,
"mani@kernel.org" <mani@kernel.org>,
"acme@kernel.org" <acme@kernel.org>,
"afaerber@suse.de" <afaerber@suse.de>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1 00/19] Intel TMA 5.1 metrics and event updates
Date: Sat, 26 Jul 2025 15:34:09 -0700 [thread overview]
Message-ID: <aIVX4RH7llNKQ4Xn@google.com> (raw)
In-Reply-To: <aIA1YubpL7wpiC0X@google.com>
On Tue, Jul 22, 2025 at 06:05:38PM -0700, Namhyung Kim wrote:
> On Tue, Jul 22, 2025 at 06:14:30PM +0000, Falcon, Thomas wrote:
> > On Fri, 2025-07-18 at 20:44 -0700, Ian Rogers wrote:
> > > Update events from:
> > > v1.31 -> v1.33 for alderlake
> > > v1.09 -> v1.12 for arrowlake
> > > v1.14 -> v1.16 for emeraldrapids
> > > v1.10 -> v1.12 for graniterpaids
> > > v1.14 -> v1.17 for lunarlake
> > > v1.14 -> v1.16 for meteorlake
> > > v1.28 -> v1.30 for sapphirerapids
> > >
> > > Update TMA 5.0 to 5.1 removing the slots event workaround as the patch series:
> > > https://lore.kernel.org/lkml/20250719030517.1990983-1-irogers@google.com/
> > > is assumed.
>
> So I'll merge this series after the above patchset.
Now I'm seeing this on my AMD machine.
Found metric 'tma_info_system_cpu_utilization'
metric expr cpu_atom@CPU_CLK_UNHALTED.REF_TSC@ / msr@tsc\,cpu\=cpu_atom@ for tma_info_system_cpu_utilization
metric expr tma_info_system_cpus_utilized / #num_cpus_online for tma_info_system_cpu_utilization
metric expr cpu_core@CPU_CLK_UNHALTED.REF_TSC@ / msr@tsc\,cpu\=cpu_core@ for tma_info_system_cpus_utilized
found event msr@tsc,cpu=cpu_core@
found event cpu_core@CPU_CLK_UNHALTED.REF_TSC@
Parsing metric events '{msr/tsc,cpu=cpu_core,metric-id=msr!3tsc!0cpu!2cpu_core!3/,cpu_core/CPU_CLK_UNHALTED.REF_TSC,metric-id=cpu_core!3CPU_CLK_UNHALTED.REF_TSC!3/}:W'
event syntax error: '{msr/tsc,cpu=cpu_core,metric-id=msr!3tsc!0cpu!2cpu_core!..'
\___ Bad event or PMU
Unable to find PMU or event on a PMU of 'msr'
event syntax error: '{msr/tsc,cpu=cpu_core,metric-id=msr!3tsc!0cpu!2cpu_core!..'
\___ not a valid PMU or CPU number
event syntax error: '{msr/tsc,cpu=cpu_core,metric-id=msr!3tsc!0cpu!2cpu_core!..'
\___ not a valid PMU or CPU number
event syntax error: '{msr/tsc,cpu=cpu_core,metric-id=msr!3tsc!0cpu!2cpu_core!..'
\___ not a valid PMU or CPU number
event syntax error: '{msr/tsc,cpu=cpu_core,metric-id=msr!3tsc!0cpu!2cpu_core!..'
\___ not a valid PMU or CPU number
Broken metric tma_info_system_cpu_utilization
---- end(-1) ----
9.3: Parsing of PMU event table metrics : FAILED!
parsing 'tma_info_mem_mix_memload_ratio': '1e3 * cpu_atom@MEM_UOPS_RETIRED.ALL_LOADS@ / cpu_atom@UOPS_RETIRED.ALL@'
parsing 'tma_info_serialization_%_tpause_cycles': '100 * cpu_atom@SERIALIZATION.C01_MS_SCB@ / (5 * cpu_atom@CPU_CLK_UNHALTED.CORE@)'
parsing 'tma_info_system_cpu_utilization': 'cpu_atom@CPU_CLK_UNHALTED.REF_TSC@ / msr@tsc\,cpu\=cpu_atom@'
check_parse_fake failed
---- end(-1) ----
9.4: Parsing of PMU event table metrics with fake PMUs : FAILED!
Thanks,
Namhyung
next prev parent reply other threads:[~2025-07-26 22:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 3:44 [PATCH v1 00/19] Intel TMA 5.1 metrics and event updates Ian Rogers
2025-07-19 3:44 ` [PATCH v1 01/19] perf vendor events: Update alderlake events/metrics Ian Rogers
2025-07-19 3:44 ` [PATCH v1 02/19] perf vendor events: Update arrowlake events/metrics Ian Rogers
2025-07-19 3:44 ` [PATCH v1 03/19] perf vendor events: Update broadwell metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 04/19] perf vendor events: Update cascadelakex metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 05/19] perf vendor events: Update emeraldrapids events/metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 06/19] perf vendor events: Update grandridge metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 07/19] perf vendor events: Update graniterapids events/metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 08/19] perf vendor events: Update haswell metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 09/19] perf vendor events: Update icelake metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 10/19] perf vendor events: Update ivybridge/ivytown metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 11/19] perf vendor events: Update jaketown metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 12/19] perf vendor events: Update lunarlake events/metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 13/19] perf vendor events: Update meteorlake events/metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 14/19] perf vendor events: Update rocketlake metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 15/19] perf vendor events: Update sandybridge metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 16/19] perf vendor events: Update sapphirerapids events/metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 17/19] perf vendor events: Update sierraforest metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 18/19] perf vendor events: Update skylake metrics Ian Rogers
2025-07-19 3:45 ` [PATCH v1 19/19] perf vendor events: Update tigerlake metrics Ian Rogers
2025-07-22 18:14 ` [PATCH v1 00/19] Intel TMA 5.1 metrics and event updates Falcon, Thomas
2025-07-23 1:05 ` Namhyung Kim
2025-07-26 22:34 ` Namhyung Kim [this message]
2025-07-28 18:12 ` Namhyung Kim
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=aIVX4RH7llNKQ4Xn@google.com \
--to=namhyung@kernel.org \
--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=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@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).