KVM: riscv: Use an rwlock for mmu_lock

Browse source

RISC-V KVM currently uses a spinlock for mmu_lock. That serializes all
G-stage MMU operations, including permission-only updates that do not
allocate or free page-table pages.

Use KVM's rwlock form of mmu_lock, as x86 and arm64 already do. Keep the
existing map, unmap and teardown paths on the write side. This prepares
RISC-V for read-side handling of G-stage permission updates.

Signed-off-by: Jinyu Tang <tjytimi@163.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Link: https://lore.kernel.org/r/20260517153427.94889-3-tjytimi@163.com
Signed-off-by: Anup Patel <anup@brainfault.org>

...

This commit is contained in:

Jinyu Tang 2026-05-17 23:34:24 +08:00 • committed by Anup Patel

parent 9090ba2e7c

commit cc98f006c6

3 changed files with 15 additions and 13 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

arch/riscv/include/asm/kvm_host.h

View file

2

arch/riscv/kvm/gstage.c

View file

24

arch/riscv/kvm/mmu.c

View file