From: Shang XiaoJing <shangxiaojing@huawei.com>
To: <john.garry@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>
Cc: <shangxiaojing@huawei.com>
Subject: [PATCH 0/3] perf vendor events arm64: Fix incorrect metrics and improve readability
Date: Fri, 21 Oct 2022 16:53:23 +0800 [thread overview]
Message-ID: <20221021085326.17139-1-shangxiaojing@huawei.com> (raw)
First fix the incorrect hip08 metrics, then add some core events to the
JSON file. Last, change the event code to the event name for improving
readability.
Shang XiaoJing (3):
perf vendor events arm64: Fix incorrect Hisi hip08 L3 metrics
perf vendor events arm64: Add HiSilicon hip08 core events
perf vendor events arm64: Use event name instead of event code
.../arm64/hisilicon/hip08/core-imp-def.json | 132 ++++++++++++++++++
.../arch/arm64/hisilicon/hip08/metrics.json | 50 +++----
2 files changed, 157 insertions(+), 25 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-10-21 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 8:53 Shang XiaoJing [this message]
2022-10-21 8:53 ` [PATCH 1/3] perf vendor events arm64: Fix incorrect Hisi hip08 L3 metrics Shang XiaoJing
2022-10-21 9:59 ` John Garry
2022-10-21 10:32 ` shangxiaojing
2022-10-21 8:53 ` [PATCH 2/3] perf vendor events arm64: Add HiSilicon hip08 core events Shang XiaoJing
2022-10-21 8:53 ` [PATCH 3/3] perf vendor events arm64: Use event name instead of event code Shang XiaoJing
2022-10-21 9:09 ` James Clark
2022-10-21 10:31 ` shangxiaojing
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=20221021085326.17139-1-shangxiaojing@huawei.com \
--to=shangxiaojing@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.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=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).