[PATCH 0/5] KVM: riscv: Speed up dirty logging write faults
patchwork-bot+linux-riscv at kernel.org
patchwork-bot+linux-riscv at kernel.org
Fri Jun 26 01:21:20 PDT 2026
Hello:
This series was applied to riscv/linux.git (fixes)
by Anup Patel <anup at brainfault.org>:
On Sun, 17 May 2026 23:34:22 +0800 you wrote:
> This series speeds up the common dirty logging write fault path for
> RISC-V KVM.
>
> When dirty logging is enabled, guest writes to write-protected G-stage
> 4K leaves currently go through the full fault path and take mmu_lock for
> write. That is expensive once the leaf already exists and
> only needs its permission and dirty state updated.
>
> [...]
Here is the summary with links:
- [1/5] KVM: riscv: Rely on common MMU notifier locking
(no matching commit)
- [2/5] KVM: riscv: Use an rwlock for mmu_lock
(no matching commit)
- [3/5] KVM: riscv: Add a G-stage PTE cmpxchg helper
https://git.kernel.org/riscv/c/7dd416fdd3fb
- [4/5] KVM: riscv: Update G-stage PTE permissions atomically
https://git.kernel.org/riscv/c/d7a26a0ba715
- [5/5] KVM: riscv: Fast-path dirty logging write faults
https://git.kernel.org/riscv/c/7705be59eb2d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
More information about the kvm-riscv
mailing list