From: John Garry <john.garry@huawei.com>
To: James Clark <james.clark@arm.com>,
<linux-perf-users@vger.kernel.org>, <acme@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <nick.forrington@arm.com>,
<al.grant@arm.com>, Will Deacon <will@kernel.org>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] perf vendor events: Add Arm Neoverse V2 PMU events
Date: Fri, 21 Oct 2022 11:47:18 +0100 [thread overview]
Message-ID: <dcf5d62d-8163-dfee-a6b7-e75207650551@huawei.com> (raw)
In-Reply-To: <20221020134512.1345013-1-james.clark@arm.com>
On 20/10/2022 14:45, James Clark wrote:
> Rename the neoverse-n2 folder to make it clear that it includes V2, and
> add V2 to mapfile.csv. V2 has the same events as N2, visible by running
> the following command in the ARM-software/data github repo [1]:
>
> diff pmu/neoverse-v2.json pmu/neoverse-n2.json | grep code
>
> Testing:
>
> $ perf test pmu
>
> 10: PMU events :
> 10.1: PMU event table sanity : Ok
> 10.2: PMU event map aliases : Ok
> 10.3: Parsing of PMU event table metrics : Ok
> 10.4: Parsing of PMU event table metrics with fake PMUs : Ok
>
> [1]:https://github.com/ARM-software/data
>
> Signed-off-by: James Clark<james.clark@arm.com>
> ---
This looks ok. Out of curiosity, do you know how the naming works for
these neoverse cores? Were "n" a predecessor to "v"?
thanks,
John
next prev parent reply other threads:[~2022-10-21 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 13:45 James Clark
2022-10-21 10:47 ` John Garry [this message]
2022-10-21 10:59 ` James Clark
2022-11-10 10:52 ` Nick Forrington
2022-11-10 18:41 ` Arnaldo Carvalho de Melo
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=dcf5d62d-8163-dfee-a6b7-e75207650551@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=al.grant@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nick.forrington@arm.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®