From: Will Deacon <will@kernel.org>
To: Paul Walmsley <pjw@kernel.org>
Cc: Atish Patra <atishp@rivosinc.com>,
Anup Patel <anup@brainfault.org>,
Mark Rutland <mark.rutland@arm.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Mayuresh Chitale <mchitale@ventanamicro.com>,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org,
Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH v6 0/8] Add SBI v3.0 PMU enhancements
Date: Mon, 15 Sep 2025 11:41:52 +0100 [thread overview]
Message-ID: <aMftcHLgBvH76erX@willie-the-truck> (raw)
In-Reply-To: <f740b716-6c8b-46a5-31ae-ecc37e766152@kernel.org>
On Mon, Sep 15, 2025 at 12:25:52AM -0600, Paul Walmsley wrote:
> On Tue, 9 Sep 2025, Atish Patra wrote:
>
> > SBI v3.0 specification[1] added two new improvements to the PMU chaper.
> > The SBI v3.0 specification is frozen and under public review phase as
> > per the RISC-V International guidelines.
> >
> > 1. Added an additional get_event_info function to query event availablity
> > in bulk instead of individual SBI calls for each event. This helps in
> > improving the boot time.
> >
> > 2. Raw event width allowed by the platform is widened to have 56 bits
> > with RAW event v2 as per new clarification in the priv ISA[2].
> >
> > Apart from implementing these new features, this series improves the gpa
> > range check in KVM and updates the kvm SBI implementation to SBI v3.0.
> >
> > The opensbi patches have been merged. This series can be found at [3].
> >
> > [1] https://github.com/riscv-non-isa/riscv-sbi-doc/releases/download/v3.0-rc7/riscv-sbi.pdf
> > [2] https://github.com/riscv/riscv-isa-manual/issues/1578
> > [3] https://github.com/atishp04/linux/tree/b4/pmu_event_info_v6
> >
> > Signed-off-by: Atish Patra <atishp@rivosinc.com>
>
> For the series:
>
> Acked-by: Paul Walmsley <pjw@kernel.org>
I was assuming this series would go via the Risc-V arch tree so please
shout if you were expecting me to take it via drivers/perf/!
Will
next prev parent reply other threads:[~2025-09-15 10:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 7:03 [PATCH v6 0/8] Add SBI v3.0 PMU enhancements Atish Patra
2025-09-09 7:03 ` [PATCH v6 1/8] drivers/perf: riscv: Add SBI v3.0 flag Atish Patra
2025-09-09 7:03 ` [PATCH v6 2/8] drivers/perf: riscv: Add raw event v2 support Atish Patra
2025-09-09 7:03 ` [PATCH v6 3/8] RISC-V: KVM: Add support for Raw event v2 Atish Patra
2025-09-09 7:03 ` [PATCH v6 4/8] drivers/perf: riscv: Implement PMU event info function Atish Patra
2025-09-09 13:08 ` Anup Patel
2025-09-09 7:03 ` [PATCH v6 5/8] drivers/perf: riscv: Export " Atish Patra
2025-09-09 7:03 ` [PATCH v6 6/8] RISC-V: KVM: No need of explicit writable slot check Atish Patra
2025-09-09 13:09 ` Anup Patel
2025-09-09 7:03 ` [PATCH v6 7/8] RISC-V: KVM: Implement get event info function Atish Patra
2025-09-09 7:03 ` [PATCH v6 8/8] RISC-V: KVM: Upgrade the supported SBI version to 3.0 Atish Patra
2025-09-15 6:25 ` [PATCH v6 0/8] Add SBI v3.0 PMU enhancements Paul Walmsley
2025-09-15 10:41 ` Will Deacon [this message]
2025-09-15 11:58 ` Anup Patel
2025-10-09 1:06 ` patchwork-bot+linux-riscv
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=aMftcHLgBvH76erX@willie-the-truck \
--to=will@kernel.org \
--cc=anup@brainfault.org \
--cc=atishp@rivosinc.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchitale@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=seanjc@google.com \
/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