From: "Liang, Kan" <kan.liang@linux.intel.com>
To: "Ian Rogers" <irogers@google.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Weilin Wang" <weilin.wang@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Perry Taylor" <perry.taylor@intel.com>,
"Samantha Alt" <samantha.alt@intel.com>,
"Caleb Biggers" <caleb.biggers@intel.com>,
"Edward Baker" <edward.baker@intel.com>,
"Michael Petlan" <mpetlan@redhat.com>,
"Thomas Falcon" <thomas.falcon@intel.com>
Subject: Re: [PATCH v2 00/23] Intel vendor events and TMA 5.01 metrics
Date: Fri, 17 Jan 2025 14:10:51 -0500 [thread overview]
Message-ID: <3d87d244-a47b-4b70-90cd-710a38aa2431@linux.intel.com> (raw)
In-Reply-To: <10984553-bf84-4bff-9129-4b31815e38d6@linux.intel.com>
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,
Kan
next prev parent reply other threads:[~2025-01-17 19:10 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 [this message]
2025-01-17 19:43 ` Ian Rogers
2025-01-17 20:30 ` Falcon, Thomas
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=3d87d244-a47b-4b70-90cd-710a38aa2431@linux.intel.com \
--to=kan.liang@linux.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=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=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