Re: [PATCH 0/5] KVM: riscv: Speed up dirty logging write faults
| Newsgroups | org.infradead.lists.kvm-riscv,org.infradead.lists.linux-riscv,org.kernel.vger.kvm,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178246208080.3816447.14235715613320602429.git-patchwork-notify@kernel.org> |
Hello: This series was applied to riscv/linux.git (fixes) by Anup Patel <[email protected]>: 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 -- kvm-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kvm-riscv