From: Ian Rogers <irogers@google.com>
To: Al Grant <al.grant@foss.arm.com>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: PMU event repository for Arm
Date: Fri, 10 Dec 2021 10:47:22 -0800 [thread overview]
Message-ID: <CAP-5=fUtkCzgsGS6LkCVTuyPmw981Dd-EavtU6uv3o7OB7CnDA@mail.gmail.com> (raw)
In-Reply-To: <486e7e8d-de21-5e26-3792-db2fd6991602@foss.arm.com>
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?
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-10 18:47 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 [this message]
2021-12-14 10:22 ` James Clark
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='CAP-5=fUtkCzgsGS6LkCVTuyPmw981Dd-EavtU6uv3o7OB7CnDA@mail.gmail.com' \
--to=irogers@google.com \
--cc=al.grant@foss.arm.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).