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, palmer@rivosinc.com,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org
Subject: Re: [PATCH 0/8] Add SBI v3.0 PMU enhancements
Date: Thu, 09 Jan 2025 19:40:40 +0000 [thread overview]
Message-ID: <173645164075.1490121.3552449186878140898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241119-pmu_event_info-v1-0-a4f9691421f8@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 19 Nov 2024 12:29:48 -0800 you wrote:
> SBI v3.0 specification[1] added two new improvements to the PMU chaper.
>
> 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].
>
> [...]
Here is the summary with links:
- [1/8] drivers/perf: riscv: Add SBI v3.0 flag
(no matching commit)
- [2/8] drivers/perf: riscv: Fix Platform firmware event data
https://git.kernel.org/riscv/c/fc58db9aeb15
- [3/8] drivers/perf: riscv: Add raw event v2 support
(no matching commit)
- [4/8] RISC-V: KVM: Add support for Raw event v2
(no matching commit)
- [5/8] drivers/perf: riscv: Implement PMU event info function
(no matching commit)
- [6/8] drivers/perf: riscv: Export PMU event info function
(no matching commit)
- [7/8] RISC-V: KVM: Implement get event info function
(no matching commit)
- [8/8] RISC-V: KVM: Upgrade the supported SBI version to 3.0
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-09 19:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 20:29 [PATCH 0/8] Add SBI v3.0 PMU enhancements Atish Patra
2024-11-19 20:29 ` [PATCH 1/8] drivers/perf: riscv: Add SBI v3.0 flag Atish Patra
2024-11-19 20:29 ` [PATCH 2/8] drivers/perf: riscv: Fix Platform firmware event data Atish Patra
2024-11-28 13:10 ` Alexandre Ghiti
2024-12-02 18:26 ` Atish Kumar Patra
2024-11-19 20:29 ` [PATCH 3/8] drivers/perf: riscv: Add raw event v2 support Atish Patra
2024-12-02 22:37 ` Samuel Holland
2024-12-03 0:15 ` Atish Kumar Patra
2024-12-03 2:39 ` Samuel Holland
2024-12-09 18:52 ` Atish Kumar Patra
2024-11-19 20:29 ` [PATCH 4/8] RISC-V: KVM: Add support for Raw event v2 Atish Patra
2024-11-19 20:29 ` [PATCH 5/8] drivers/perf: riscv: Implement PMU event info function Atish Patra
2024-12-02 22:49 ` Samuel Holland
2024-12-10 1:16 ` Atish Kumar Patra
2024-11-19 20:29 ` [PATCH 6/8] drivers/perf: riscv: Export " Atish Patra
2024-11-19 20:29 ` [PATCH 7/8] RISC-V: KVM: Implement get " Atish Patra
2024-12-02 23:02 ` Samuel Holland
2024-12-10 1:16 ` Atish Kumar Patra
2024-11-19 20:29 ` [PATCH 8/8] RISC-V: KVM: Upgrade the supported SBI version to 3.0 Atish Patra
2025-01-09 19:40 ` 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=173645164075.1490121.3552449186878140898.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=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.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