From: John Garry <john.garry@huawei.com>
To: Shang XiaoJing <shangxiaojing@huawei.com>, <will@kernel.org>,
<james.clark@arm.com>, <mike.leach@linaro.org>,
<leo.yan@linaro.org>, <peterz@infradead.org>, <mingo@redhat.com>,
<acme@kernel.org>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <jolsa@kernel.org>,
<namhyung@kernel.org>, <kjain@linux.ibm.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] perf vendor events arm64: Use event name instead of event code
Date: Wed, 26 Oct 2022 10:25:58 +0100 [thread overview]
Message-ID: <e58aada8-fa83-ac87-fdec-f64a76a9817c@huawei.com> (raw)
In-Reply-To: <20221021105035.10000-4-shangxiaojing@huawei.com>
On 21/10/2022 11:50, Shang XiaoJing wrote:
> Use the event name instead of the corresponding event code for more
> clear, which makes the result of perf more readable.
>
> Signed-off-by: Shang XiaoJing<shangxiaojing@huawei.com>
> Acked-by: James Clark<james.clark@arm.com>
Uh, you prob could have added these in patch 2/3. anyway,
Reviewed-by: John Garry <john.garry@huawei.com>
prev parent reply other threads:[~2022-10-26 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 10:50 [PATCH v2 0/3] perf vendor events arm64: Fix incorrect metrics and improve readability Shang XiaoJing
2022-10-21 10:50 ` [PATCH v2 1/3] perf vendor events arm64: Fix incorrect Hisi hip08 L3 metrics Shang XiaoJing
2022-10-26 9:07 ` John Garry
2022-10-26 14:03 ` Arnaldo Carvalho de Melo
2022-10-21 10:50 ` [PATCH v2 2/3] perf vendor events arm64: Add HiSilicon hip08 core events Shang XiaoJing
2022-10-26 9:23 ` John Garry
2022-10-21 10:50 ` [PATCH v2 3/3] perf vendor events arm64: Use event name instead of event code Shang XiaoJing
2022-10-26 9:25 ` John Garry [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=e58aada8-fa83-ac87-fdec-f64a76a9817c@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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=peterz@infradead.org \
--cc=shangxiaojing@huawei.com \
--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).