From: Will Deacon <will.deacon@arm.com>
To: John Garry <john.garry@huawei.com>
Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>,
Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>,
linux-kernel@vger.kernel.org, linuxarm@huawei.com,
jonathan.cameron@huawei.com,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [PATCH] perf vendor events arm64: Add hip08 implementation defined PMU core events
Date: Wed, 18 Oct 2017 11:49:11 +0100 [thread overview]
Message-ID: <20171018104910.GB11669@arm.com> (raw)
In-Reply-To: <c4be39b9-ba1a-0db6-16f3-fafc99ad190d@huawei.com>
On Wed, Oct 18, 2017 at 10:25:39AM +0100, John Garry wrote:
> On 17/10/2017 13:59, Will Deacon wrote:
> >Hi Shaokun,
> >
> >Thanks for the patch. One comment below.
> >
> >On Tue, Oct 17, 2017 at 03:01:39PM +0800, Shaokun Zhang wrote:
> >>This is a short list of useful implementation defined PMU events of
> >>hip08, other supported events are not listed in this JSON file.
> >>
> >>This patch is dependent on Cavium's patch-v9 (Add support for
> >>ThunderX2 pmu events using json files), Link:
> >>https://www.spinics.net/lists/arm-kernel/msg611895.html
> >>
> >>Signed-off-by: Shaokun Zhang <zhangshaokun@hisilicon.com>
> >>Cc: Peter Zijlstra <peterz@infradead.org>
> >>Cc: Ingo Molnar <mingo@redhat.com>
> >>Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> >>Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> >>Cc: Will Deacon <will.deacon@arm.com>
> >>Cc: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
> >>Cc: John Garry <john.garry@huawei.com>
> >>---
> >> .../arch/arm64/hisilicon/hip08-imp-def.json | 176 +++++++++++++++++++++
> >> tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 +
> >> 2 files changed, 177 insertions(+)
> >> create mode 100644 tools/perf/pmu-events/arch/arm64/hisilicon/hip08-imp-def.json
> >>
> >>diff --git a/tools/perf/pmu-events/arch/arm64/hisilicon/hip08-imp-def.json b/tools/perf/pmu-events/arch/arm64/hisilicon/hip08-imp-def.json
> >>new file mode 100644
> >>index 0000000..6bb31da
> >>--- /dev/null
> >>+++ b/tools/perf/pmu-events/arch/arm64/hisilicon/hip08-imp-def.json
> >>@@ -0,0 +1,176 @@
> >>+[
> >>+ {
> >>+ "PublicDescription": "Attributable Level 1 data cache access, read",
> >>+ "EventCode": "0x40",
> >>+ "EventName": "L1D_CACHE_RD",
> >>+ "BriefDescription": "L1D cache access, read",
> >>+ },
> >>+ {
> >>+ "PublicDescription": "Attributable Level 1 data cache access, write",
> >>+ "EventCode": "0x41",
> >>+ "EventName": "L1D_CACHE_WR",
> >>+ "BriefDescription": "L1D cache access, write",
> >>+ },
> >
> >So these are the same as the events in cavium/thunderx2-imp-def.json and
> >should be factored out. In fact, ARM recommends event numbers for 0x40-0xBF,
> >so the best thing would be to have those defined in their own file, then
> >have a way for the various CPU-specific .json files to pick and chose the
> >events they need from there.
>
> Right, this seems reasonable. Just need to check on feasible.
>
> In terms of coordinating this work, shall we do it? Will arm64+ThunderX
> support be accepted as is?
Yes, that would be my preference if you don't mind.
Will
next prev parent reply other threads:[~2017-10-18 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 7:01 [PATCH] perf vendor events arm64: Add hip08 implementation defined PMU core events Shaokun Zhang
2017-10-17 12:59 ` Will Deacon
2017-10-18 9:25 ` John Garry
2017-10-18 10:49 ` Will Deacon [this message]
2017-10-18 16:37 ` John Garry
2017-10-18 17:04 ` Will Deacon
2017-10-19 9:20 ` John Garry
2017-10-18 17:20 ` Ganapatrao Kulkarni
2017-10-19 10:29 ` John Garry
2017-10-25 10:06 ` Ganapatrao Kulkarni
2017-10-25 11:07 ` John Garry
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=20171018104910.GB11669@arm.com \
--to=will.deacon@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ganapatrao.kulkarni@cavium.com \
--cc=john.garry@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=zhangshaokun@hisilicon.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