From: Jiri Olsa <jolsa@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, will@kernel.org,
linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com,
irogers@google.com, ak@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] perf: Improve list for arm64
Date: Wed, 17 Jun 2020 12:36:37 +0200 [thread overview]
Message-ID: <20200617103637.GD2210496@krava> (raw)
In-Reply-To: <1592384514-119954-1-git-send-email-john.garry@huawei.com>
On Wed, Jun 17, 2020 at 05:01:52PM +0800, John Garry wrote:
> This couple of patches provides:
> - aliases for arm64 CPU core events in perf list, like x86
> - ensures that CPU core events are not sparsely listed
>
> Differences to v1:
> - Add ack from Namhyung Kim (thanks)
> - use more concise logic in patch 2/2 and also add comment
>
> John Garry (2):
> perf pmu: List kernel supplied event aliases for arm64
> perf pmu: Improve CPU core PMU HW event list ordering
Acked-by: Jiri Olsa <jolsa@redhat.com>
thanks,
jirka
>
> tools/perf/util/pmu.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> --
> 2.26.2
>
prev parent reply other threads:[~2020-06-17 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 9:01 [PATCH v2 0/2] perf: Improve list for arm64 John Garry
2020-06-17 9:01 ` [PATCH v2 1/2] perf pmu: List kernel supplied event aliases " John Garry
2020-06-17 9:01 ` [PATCH v2 2/2] perf pmu: Improve CPU core PMU HW event list ordering John Garry
2020-06-17 11:31 ` Namhyung Kim
2020-06-17 12:15 ` Arnaldo Carvalho de Melo
2020-08-03 8:00 ` John Garry
2020-08-03 12:54 ` Arnaldo Carvalho de Melo
2020-08-03 13:23 ` John Garry
2020-06-17 10:36 ` Jiri Olsa [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=20200617103637.GD2210496@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).