From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: Andrew Kilroy <andrew.kilroy@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Will Deacon <will@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Leo Yan <leo.yan@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] perf vendor events: Categorise the Neoverse V1 counters
Date: Wed, 13 Oct 2021 12:28:50 -0300 [thread overview]
Message-ID: <YWb7Mrh8QYSMgPjl@kernel.org> (raw)
In-Reply-To: <03152b9d-2ad1-7bd3-e5a7-fc899c8c567c@huawei.com>
Em Wed, Oct 06, 2021 at 09:38:27AM +0100, John Garry escreveu:
> On 06/10/2021 09:11, Andrew Kilroy wrote:
> > This is so they are categorised in the perf list output. The pmus all
> > exist in the armv8-common-and-microarch.json and arm-recommended.json
> > files, so this commit places them into each category's own file under
> >
> > tools/perf/pmu-events/arch/arm64/arm/neoverse-v1
> >
> > Also add the Neoverse V1 to the arm64 mapfile
> >
> > Signed-off-by: Andrew Kilroy<andrew.kilroy@arm.com>
> > ---
>
> Reviewed-by: John Garry <john.garry@huawei.com>
>
> Note: for the other 2x patches in the series, you should have picked up my
> reviewed-by tag for v2 (unless they have changed significantly from when the
> tag was originally granted).
Right, I'm picking it up this time, thanks!
- Arnaldo
prev parent reply other threads:[~2021-10-13 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 8:11 [PATCH v2 1/3] perf vendor events: Syntax corrections in Neoverse N1 json Andrew Kilroy
2021-10-06 8:11 ` [PATCH v2 2/3] perf vendor events: Add new armv8 pmu events Andrew Kilroy
2021-10-06 8:11 ` [PATCH v2 3/3] perf vendor events: Categorise the Neoverse V1 counters Andrew Kilroy
2021-10-06 8:38 ` John Garry
2021-10-06 8:43 ` Andrew Kilroy
2021-10-13 15:28 ` Arnaldo Carvalho de Melo [this message]
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=YWb7Mrh8QYSMgPjl@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.kilroy@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--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=mathieu.poirier@linaro.org \
--cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).