From: Ji Sheng Teoh <jisheng.teoh@starfivetech.com>
To: <irogers@google.com>
Cc: <acme@kernel.org>, <adrian.hunter@intel.com>,
<alexander.shishkin@linux.intel.com>, <aou@eecs.berkeley.edu>,
<jisheng.teoh@starfivetech.com>, <jolsa@kernel.org>,
<leyfoon.tan@starfivetech.com>, <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <mark.rutland@arm.com>,
<mingo@redhat.com>, <n.shubin@yadro.com>, <namhyung@kernel.org>,
<palmer@dabbelt.com>, <paul.walmsley@sifive.com>,
<peterz@infradead.org>
Subject: Re: [PATCH v3] perf vendor events riscv: add StarFive Dubhe-90 JSON file
Date: Wed, 22 Nov 2023 00:53:39 +0800 [thread overview]
Message-ID: <20231121165339.2177083-1-jisheng.teoh@starfivetech.com> (raw)
In-Reply-To: <CAP-5=fVgD7sc1uP5G-Q_bo8bf82rncFt=LLTA725csAT7g63rA@mail.gmail.com>
On Tue, 21 Nov 2023 07:25:21 -0800
Ian Rogers <irogers@google.com> wrote:
> On Wed, Nov 8, 2023 at 11:51 PM Ji Sheng Teoh
> <jisheng.teoh@starfivetech.com> wrote:
> >
> > StarFive's Dubhe-90 supports raw event id 0x00 - 0x22.
> > The raw events are enabled through PMU node of DT binding.
> > Besides raw event, add standard RISC-V firmware events to
> > support monitoring of firmware event.
> >
> > Example of PMU DT node:
> > pmu {
> > compatible = "riscv,pmu";
> > riscv,raw-event-to-mhpmcounters =
> > /* Event ID 1-31 */
> > <0x00 0x00 0xFFFFFFFF 0xFFFFFFE0 0x00007FF8>,
> > /* Event ID 32-33 */
> > <0x00 0x20 0xFFFFFFFF 0xFFFFFFFE 0x00007FF8>,
> > /* Event ID 34 */
> > <0x00 0x22 0xFFFFFFFF 0xFFFFFF22 0x00007FF8>;
> > };
> >
> > Perf stat output:
> > [root@user]# perf stat -a \
> > -e access_mmu_stlb \
> > -e miss_mmu_stlb \
> > -e access_mmu_pte_c \
> > -e rob_flush \
> > -e btb_prediction_miss \
> > -e itlb_miss \
> > -e sync_del_fetch_g \
> > -e icache_miss \
> > -e bpu_br_retire \
> > -e bpu_br_miss \
> > -e ret_ins_retire \
> > -e ret_ins_miss \
> > -- openssl speed rsa2048
> > Doing 2048 bits private rsa's for 10s: 39 2048 bits private RSA's in
> > 10.03s
> > Doing 2048 bits public rsa's for 10s: 1469 2048 bits public RSA's in
> > 9.47s
> > version: 3.0.10
> > built on: Tue Aug 1 13:47:24 2023 UTC
> > options: bn(64,64)
> > CPUINFO: N/A
> > sign verify sign/s verify/s
> > rsa 2048 bits 0.257179s 0.006447s 3.9 155.1
> >
> > Performance counter stats for 'system wide':
> >
> > 3112882 access_mmu_stlb
> > 10550 miss_mmu_stlb
> > 18251 access_mmu_pte_c
> > 274765 rob_flush
> > 22470560 btb_prediction_miss
> > 3035839 itlb_miss
> > 643549060 sync_del_fetch_g
> > 133013 icache_miss
> > 62982796 bpu_br_retire
> > 287548 bpu_br_miss
> > 8935910 ret_ins_retire
> > 8308 ret_ins_miss
> >
> > 20.656182600 seconds time elapsed
> >
> > Signed-off-by: Ji Sheng Teoh <jisheng.teoh@starfivetech.com>
> > Reviewed-by: Ley Foon Tan <leyfoon.tan@starfivetech.com>
> > ---
> > Changelog:
> > v2 -> v3:
> > - Add standard RISC-V firmware event
> > - Update commit message to reflect addition of standard
> > RISC-V firmware event.
> > v1 -> v2:
> > - Rename 'Starfive Dubhe' to 'StarFive Dubhe-90' in commit message.
> > - Rename 'starfive/dubhe' pmu-events folder to 'starfive/dubhe-90'
> > - Update MARCHID to 0x80000000db000090 in mapfile.csv
> > ---
> > tools/perf/pmu-events/arch/riscv/mapfile.csv | 1 +
> > .../arch/riscv/starfive/dubhe-90/common.json | 172
> > ++++++++++++++++++ .../riscv/starfive/dubhe-90/firmware.json |
> > 68 +++++++ 3 files changed, 241 insertions(+)
> > create mode 100644
> > tools/perf/pmu-events/arch/riscv/starfive/dubhe-90/common.json
> > create mode 100644
> > tools/perf/pmu-events/arch/riscv/starfive/dubhe-90/firmware.json
> >
> > diff --git a/tools/perf/pmu-events/arch/riscv/mapfile.csv
> > b/tools/perf/pmu-events/arch/riscv/mapfile.csv index
> > c61b3d6ef616..5b75ecfe206d 100644 ---
> > a/tools/perf/pmu-events/arch/riscv/mapfile.csv +++
> > b/tools/perf/pmu-events/arch/riscv/mapfile.csv @@ -15,3 +15,4 @@
> > #
> > #MVENDORID-MARCHID-MIMPID,Version,Filename,EventType
> > 0x489-0x8000000000000007-0x[[:xdigit:]]+,v1,sifive/u74,core
> > +0x67e-0x80000000db000090-0x[[:xdigit:]]+,v1,starfive/dubhe-90,core
> >
>
> I've no problem with this approach, but dubhe-90's json files match
> dubhe-80s. Those files are available in perf-tools-next:
> https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/tree/tools/perf/pmu-events/arch/riscv/starfive/dubhe-80?h=perf-tools-next
> It could be useful to rebase the patch on that branch to make it
> easier to merge. As the files match you could make the regular
> expression for dubhe-80 match both of them like:
>
> 0x67e-0x80000000db0000[89]0-0x[[:xdigit:]]+,v1,starfive/dubhe-80,core
>
> Thanks,
> Ian
Thanks Ian. The suggestion makes sense, will take it in and rebase in
v4.
prev parent reply other threads:[~2023-11-21 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 7:49 Ji Sheng Teoh
2023-11-21 15:25 ` Ian Rogers
2023-11-21 16:53 ` Ji Sheng Teoh [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=20231121165339.2177083-1-jisheng.teoh@starfivetech.com \
--to=jisheng.teoh@starfivetech.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=n.shubin@yadro.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.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®