From: Xing Zhengjun <zhengjun.xing@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
perry.taylor@intel.com, caleb.biggers@intel.com,
kshipra.bopardikar@intel.com, samantha.alt@intel.com,
ahmad.yasin@intel.com, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
John Garry <john.garry@huawei.com>,
James Clark <james.clark@arm.com>,
Kajol Jain <kjain@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Miaoqian Lin <linmq006@gmail.com>,
Florian Fischer <florian.fischer@muhq.space>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v1 05/22] perf vendor events: Update Intel alderlake
Date: Thu, 29 Sep 2022 16:12:51 +0800 [thread overview]
Message-ID: <dd33559e-5d55-9866-136f-554466c0c44f@linux.intel.com> (raw)
In-Reply-To: <CAP-5=fUogKZx6JP_vg+6ti+BnbEcX+3Wnzi077s4VgxEKLpQeQ@mail.gmail.com>
On 9/29/2022 10:23 AM, Ian Rogers wrote:
> On Wed, Sep 28, 2022 at 7:08 AM Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
>>
>> Em Wed, Sep 28, 2022 at 04:22:53PM +0800, Xing Zhengjun escreveu:
>>> On 9/28/2022 3:21 PM, Ian Rogers wrote:
>>>> diff --git a/tools/perf/pmu-events/arch/x86/mapfile.csv b/tools/perf/pmu-events/arch/x86/mapfile.csv
>>>> index 7f2d777fd97f..594c6e96f0ce 100644
>>>> --- a/tools/perf/pmu-events/arch/x86/mapfile.csv
>>>> +++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
>>>> @@ -1,5 +1,5 @@
>>>> Family-model,Version,Filename,EventType
>>>> -GenuineIntel-6-9[7A],v1.13,alderlake,core
>>>> +GenuineIntel-6-(97|9A|B7|BA|BF),v1.15,alderlake,core
>>>
>>> The commit description should mention this change "Add more CPUID support
>>> for ADL"
>>
>> I added this note, with that can I have your Reviewed-by or Acked-by?
>>
>> - Arnaldo
>
> I think I should send a v2. I can add this then. Other things for v2 are:
> - this week there will likely be an update to [1] which is implicitly
> integrated here.
> - the topdown metrics are all percentages but are currently values
> zero to 1. It is straightforward to add a ScaleUnit of 100% to them
> all.
> - eyeballing topdown event metrics like:
>
> {
> "BriefDescription": "This category represents fraction of slots
> utilized by useful work i.e. issued uops that eventually get retired",
> "MetricExpr": "topdown\\-retiring / (topdown\\-fe\\-bound +
> topdown\\-bad\\-spec + topdown\\-retiring + topdown\\-be\\-bound)",
> "MetricGroup": "TopdownL1;tma_L1_group",
> "MetricName": "tma_retiring",
> ...
> it looks like the group will fail due to the missing slots event. This
> can be fixed with:
> "MetricExpr": "topdown\\-retiring / (topdown\\-fe\\-bound +
> topdown\\-bad\\-spec + topdown\\-retiring + topdown\\-be\\-bound) + 0
> * TOPDOWN.SLOTS",
>
> Thanks,
> Ian
I just test all the events for SPR/ADL, no error find.
But there are a lots of metrics fail due to slots missed.
|0929_005708.420|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_branch_mispredicts" -a sleep 0.1 failed. Return code is 255|
|0929_005709.221|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_backend_bound" -a sleep 0.1 failed. Return code is 255|
|0929_005709.544|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_memory_bound" -a sleep 0.1 failed. Return code is 255|
|0929_005723.757|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_core_bound" -a sleep 0.1 failed. Return code is 255|
|0929_005724.531|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_ports_utilization" -a sleep 0.1 failed. Return code is 255|
|0929_005731.541|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_retiring" -a sleep 0.1 failed. Return code is 255|
|0929_005731.860|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_light_operations" -a sleep 0.1 failed. Return code is 255|
|0929_005732.811|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_x87_use" -a sleep 0.1 failed. Return code is 255|
|0929_005741.026|ERROR| common.sh:123:do_cmd() - perf stat -M
"tma_heavy_operations" -a sleep 0.1 failed. Return code is 255|
|0929_005746.165|ERROR| common.sh:123:do_cmd() - perf stat -M
"Memory_Latency" -a sleep 0.1 failed. Return code is 255|
# perf stat -v -M "tma_branch_mispredicts" -a sleep 1
Using CPUID GenuineIntel-6-8F-3
metric expr topdown\-br\-mispredict / (topdown\-fe\-bound +
topdown\-bad\-spec + topdown\-retiring + topdown\-be\-bound) for
tma_branch_mispredicts
found event topdown-retiring
found event topdown-fe-bound
found event topdown-be-bound
found event topdown-br-mispredict
found event topdown-bad-spec
Parsing metric events
'{topdown-retiring/metric-id=topdown!1retiring/,topdown-fe-bound/metric-id=topdown!1fe!1bound/,topdown-be-bound/metric-id=topdown!1be!1bound/,topdown-br-mispredict/metric-id=topdown!1br!1mispredict/,topdown-bad-spec/metric-id=topdown!1bad!1spec/}:W'
topdown-retiring -> cpu/event=0,umask=0x80/
topdown-fe-bound -> cpu/event=0,umask=0x82/
topdown-be-bound -> cpu/event=0,umask=0x83/
topdown-br-mispredict -> cpu/event=0,umask=0x85/
topdown-bad-spec -> cpu/event=0,umask=0x81/
Control descriptor is not initialized
Warning:
topdown-retiring event is not supported by the kernel.
Error:
The sys_perf_event_open() syscall returned with 22 (Invalid argument)
for event (topdown-retiring).
/bin/dmesg | grep -i perf may provide additional information.
>
> [1] https://github.com/intel/perfmon-metrics
>
>>>> GenuineIntel-6-(1C|26|27|35|36),v4,bonnell,core
>>>> GenuineIntel-6-(3D|47),v26,broadwell,core
>>>> GenuineIntel-6-56,v23,broadwellde,core
>>>
>>> --
>>> Zhengjun Xing
>>
>> --
>>
>> - Arnaldo
--
Zhengjun Xing
next prev parent reply other threads:[~2022-09-29 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 7:21 [PATCH v1 00/22] Improvements to Intel perf metrics Ian Rogers
2022-09-28 7:21 ` [PATCH v1 01/22] perf expr: Allow a double if expression Ian Rogers
2022-09-28 7:21 ` [PATCH v1 02/22] perf expr: Remove jevents case workaround Ian Rogers
2022-09-28 7:21 ` [PATCH v1 03/22] perf metrics: Don't scale counts going into metrics Ian Rogers
2022-09-29 8:48 ` Xing Zhengjun
2022-10-04 1:34 ` Ian Rogers
2022-09-28 7:21 ` [PATCH v1 06/22] perf vendor events: Update Intel broadwell Ian Rogers
2022-09-28 7:21 ` [PATCH v1 07/22] perf vendor events: Update Intel broadwellx Ian Rogers
2022-09-28 7:21 ` [PATCH v1 09/22] perf vendor events: Update elkhartlake cpuids Ian Rogers
2022-09-28 7:21 ` [PATCH v1 10/22] perf vendor events: Update Intel haswell Ian Rogers
2022-09-28 7:21 ` [PATCH v1 12/22] perf vendor events: Update Intel icelake Ian Rogers
2022-09-28 7:21 ` [PATCH v1 14/22] perf vendor events: Update Intel ivybridge Ian Rogers
2022-09-28 7:21 ` [PATCH v1 16/22] perf vendor events: Update Intel jaketown Ian Rogers
2022-09-28 7:21 ` [PATCH v1 17/22] perf vendor events: Update Intel sandybridge Ian Rogers
2022-09-28 7:22 ` [PATCH v1 19/22] perf vendor events: Update silvermont cpuids Ian Rogers
2022-09-28 7:22 ` [PATCH v1 21/22] perf vendor events: Update Intel tigerlake Ian Rogers
2022-09-28 7:22 ` [PATCH v1 22/22] perf vendor events: Update Intel broadwellde Ian Rogers
2022-09-28 12:56 ` [PATCH v1 00/22] Improvements to Intel perf metrics Liang, Kan
2022-09-28 14:04 ` Ian Rogers
2022-09-28 15:05 ` Liang, Kan
[not found] ` <20220928072204.1613330-6-irogers@google.com>
[not found] ` <44f59d7c-ced7-2d74-edbc-f354047339fe@linux.intel.com>
2022-09-28 14:07 ` [PATCH v1 05/22] perf vendor events: Update Intel alderlake Arnaldo Carvalho de Melo
2022-09-29 2:23 ` Ian Rogers
2022-09-29 8:12 ` Xing Zhengjun [this message]
2022-09-29 13:00 ` Arnaldo Carvalho de Melo
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=dd33559e-5d55-9866-136f-554466c0c44f@linux.intel.com \
--to=zhengjun.xing@linux.intel.com \
--cc=acme@kernel.org \
--cc=ahmad.yasin@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=eranian@google.com \
--cc=florian.fischer@muhq.space \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=kshipra.bopardikar@intel.com \
--cc=linmq006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@intel.com \
--cc=tmricht@linux.ibm.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).