From: John Garry <john.garry@huawei.com>
To: <James.Clark@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>, <seanvk.dev@oregontracks.org>,
Florian Fainelli <f.fainelli@gmail.com>, <wcohen@redhat.com>,
Ganapatrao Kulkarni <gklkml16@gmail.com>,
Will Deacon <will@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: perf tool pmuevents: About arm64 a76 JSON
Date: Wed, 2 Oct 2019 16:37:00 +0100 [thread overview]
Message-ID: <749a0b8e-2bfd-28f6-b34d-dc72ef3d3a74@huawei.com> (raw)
Hi,
I noticed that the JSON to support a76 pmu events was added recently.
May I ask why we add explicit support for the common architectural and
microarch events (event id 0x0-0x3f), when they would be already
available from the kernel pmuv3 driver?
The ampere emag jsons do similar. Others don't.
The only advantage I see is that we have an event description, but I am
sure how useful that is.
Cheers,
John
reply other threads:[~2019-10-02 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=749a0b8e-2bfd-28f6-b34d-dc72ef3d3a74@huawei.com \
--to=john.garry@huawei.com \
--cc=James.Clark@arm.com \
--cc=acme@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gklkml16@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=seanvk.dev@oregontracks.org \
--cc=wcohen@redhat.com \
--cc=will@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).