From: patchwork-bot+linux-riscv@kernel.org
To: Atish Kumar Patra <atishp@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
will@kernel.org, mark.rutland@arm.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, mchitale@ventanamicro.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, seanjc@google.com
Subject: Re: [PATCH v6 0/8] Add SBI v3.0 PMU enhancements
Date: Thu, 09 Oct 2025 01:06:57 +0000 [thread overview]
Message-ID: <175997201703.3661959.2204934721349838885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250909-pmu_event_info-v6-0-d8f80cacb884@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Anup Patel <anup@brainfault.org>:
On Tue, 09 Sep 2025 00:03:19 -0700 you 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.
>
> [...]
Here is the summary with links:
- [v6,1/8] drivers/perf: riscv: Add SBI v3.0 flag
https://git.kernel.org/riscv/c/8c8d0f002b76
- [v6,2/8] drivers/perf: riscv: Add raw event v2 support
https://git.kernel.org/riscv/c/656ef2ea30a9
- [v6,3/8] RISC-V: KVM: Add support for Raw event v2
https://git.kernel.org/riscv/c/190b74154299
- [v6,4/8] drivers/perf: riscv: Implement PMU event info function
https://git.kernel.org/riscv/c/adffbd06d003
- [v6,5/8] drivers/perf: riscv: Export PMU event info function
https://git.kernel.org/riscv/c/880fcc329e24
- [v6,6/8] RISC-V: KVM: No need of explicit writable slot check
https://git.kernel.org/riscv/c/41f4d0cc331a
- [v6,7/8] RISC-V: KVM: Implement get event info function
https://git.kernel.org/riscv/c/e309fd113b9f
- [v6,8/8] RISC-V: KVM: Upgrade the supported SBI version to 3.0
https://git.kernel.org/riscv/c/dbdadd943a27
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
--
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv
prev parent reply other threads:[~2025-10-09 1:07 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
2025-09-15 11:58 ` Anup Patel
2025-10-09 1:06 ` patchwork-bot+linux-riscv [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=175997201703.3661959.2204934721349838885.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@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=seanjc@google.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).