From: James Clark <james.clark@arm.com>
To: Ian Rogers <irogers@google.com>, Al Grant <al.grant@foss.arm.com>,
Andrew Kilroy <andrew.kilroy@arm.com>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: PMU event repository for Arm
Date: Tue, 14 Dec 2021 10:22:56 +0000 [thread overview]
Message-ID: <ba55b083-dbfe-d069-ad67-0322b79112a3@arm.com> (raw)
In-Reply-To: <CAP-5=fUtkCzgsGS6LkCVTuyPmw981Dd-EavtU6uv3o7OB7CnDA@mail.gmail.com>
On 10/12/2021 18:47, Ian Rogers wrote:
> This is very helpful! It is a bit strange seeing the event codes not
> as hex. Do you have any plans around metrics? What is the flow from
> this json to the linux/tools/perf json?
Hi Ian,
I can't answer about the metrics part, but we do currently have an internal
script to convert from this repo to the perf tools jsons. Maybe @Andrew
can clarify what the plan to upstream this is. I think we struggled to
find a suitable place to put it.
James
>
> Thanks,
> Ian
>
> On Fri, Dec 10, 2021 at 7:53 AM Al Grant <al.grant@foss.arm.com> wrote:
>>
>> Hi, other vendors have shown the value of having a machine-readable
>> collection of PMU events, and we now have this for Arm:
>>
>> https://github.com/ARM-software/data
>>
>> This is equivalent to the tables in about 40 of Arm's public CPU
>> reference manuals. It includes some details that aren't needed in
>> tools/perf/pmu-events, but one could be generated from the other.
>>
>> There's also a map of CPU ids (MIDR) to CPU names, and an example
>> script to scan /proc/cpuinfo and retrieve the correct JSON file(s).
>>
>> I won't spam linux-perf-users every time we add something, but we
>> haven't publicized this before, so here it is. Feedback is welcome.
>>
>> Al
next prev parent reply other threads:[~2021-12-14 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 15:52 PMU event repository for Arm Al Grant
2021-12-10 18:47 ` Ian Rogers
2021-12-14 10:22 ` James Clark [this message]
2021-12-14 18:26 ` Ian Rogers
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=ba55b083-dbfe-d069-ad67-0322b79112a3@arm.com \
--to=james.clark@arm.com \
--cc=al.grant@foss.arm.com \
--cc=andrew.kilroy@arm.com \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
/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).