From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Andi Kleen <ak@linux.intel.com>,
James Clark <james.clark@arm.com>,
John Garry <john.garry@huawei.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Cc: Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 03/26] perf vendor events: Update metrics for Broadwell DE
Date: Mon, 31 Jan 2022 08:53:52 -0500 [thread overview]
Message-ID: <c574f164-e1f4-0166-492d-b5feaf219f54@linux.intel.com> (raw)
In-Reply-To: <20220129080929.837293-4-irogers@google.com>
On 1/29/2022 3:09 AM, Ian Rogers wrote:
> Based on TMA_metrics-full.csv version 4.3 at 01.org:
> https://download.01.org/perfmon/
> Events are still at version 7:
> https://download.01.org/perfmon/BDW-DE
> Json files generated by:
> https://github.com/intel/event-converter-for-linux-perf
>
> This adds TopdownL1_SMT metrics to bdwde-metrics.json as
> generated by the extract-tmam.py script.
>
> Tested:
> ...
> 6: Parse event definition strings : Ok
> 7: Simple expression parser : Ok
> ...
> 9: Parse perf pmu format : Ok
> 10: PMU events :
> 10.1: PMU event table sanity : Ok
> 10.2: PMU event map aliases : Ok
> 10.3: Parsing of PMU event table metrics : Skip (some metrics failed)
> 10.4: Parsing of PMU event table metrics with fake PMUs : Ok
> ...
> 68: Parse and process metrics : Ok
> ...
> 88: perf stat metrics (shadow stat) test : Ok
> 89: perf all metricgroups test : FAILED!
> 90: perf all metrics test : FAILED!
> 91: perf all PMU test : Ok
> ...
> The failures/skips relate to:
> event syntax error: '{arb/event=0x84,umask=0x1,metric-id=arb!3event!20x84!0umask!20x1!3/,arb/even..'
> \___ Cannot find PMU `arb'. Missing kernel support?
>
ARB is an uncore unit for client platforms. Broadwell DE should be a
server platform. It looks like an issue of TMA_metrics-full.csv.
I will check and see whether we can fix the TMA file.
Thanks,
Kan
> Signed-off-by: Ian Rogers<irogers@google.com>
> ---
> .../arch/x86/broadwellde/bdwde-metrics.json | 401 +++-
> .../arch/x86/broadwellde/cache.json | 1122 +++++-----
> .../arch/x86/broadwellde/floating-point.json | 222 +-
> .../arch/x86/broadwellde/frontend.json | 335 +--
> .../arch/x86/broadwellde/memory.json | 608 +++---
> .../arch/x86/broadwellde/other.json | 28 +-
> .../arch/x86/broadwellde/pipeline.json | 1892 ++++++++---------
> .../arch/x86/broadwellde/virtual-memory.json | 394 ++--
> 8 files changed, 2646 insertions(+), 2356 deletions(-)
next prev parent reply other threads:[~2022-01-31 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 8:09 [PATCH 00/26] Update Intel events and metrics Ian Rogers
2022-01-29 8:09 ` [PATCH 01/26] perf test: Allow skip for all metrics test Ian Rogers
2022-01-29 8:09 ` [PATCH 23/26] perf vendor events: Update Tigerlake Ian Rogers
[not found] ` <20220129080929.837293-4-irogers@google.com>
2022-01-31 13:53 ` Liang, Kan [this message]
2022-01-31 18:59 ` [PATCH 03/26] perf vendor events: Update metrics for Broadwell DE Ian Rogers
2022-01-31 14:04 ` [PATCH 00/26] Update Intel events and metrics Liang, Kan
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=c574f164-e1f4-0166-492d-b5feaf219f54@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=zhengjun.xing@linux.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).