[<prev] [next>] [day] [month] [year] [list]
Message-ID: <749a0b8e-2bfd-28f6-b34d-dc72ef3d3a74@huawei.com>
Date: Wed, 2 Oct 2019 16:37:00 +0100
From: John Garry <john.garry@...wei.com>
To: <James.Clark@....com>
CC: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
<seanvk.dev@...gontracks.org>,
Florian Fainelli <f.fainelli@...il.com>, <wcohen@...hat.com>,
Ganapatrao Kulkarni <gklkml16@...il.com>,
Will Deacon <will@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: perf tool pmuevents: About arm64 a76 JSON
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
Powered by blists - more mailing lists