aboutsummaryrefslogtreecommitdiffstats
path: root/arch/riscv/kvm/vcpu_vector.c
diff options
context:
space:
mode:
authorDaniel Henrique Barboza <[email protected]>2023-08-03 16:33:00 +0000
committerAnup Patel <[email protected]>2023-08-08 11:55:58 +0000
commit1099c80906d358db542c64aba370291ae4b932b7 (patch)
treefe6a1519846b8bfeb703a9247601ac07e342193d /arch/riscv/kvm/vcpu_vector.c
parentRISC-V: KVM: avoid EBUSY when writing the same machine ID val (diff)
downloadkernel-1099c80906d358db542c64aba370291ae4b932b7.tar.gz
kernel-1099c80906d358db542c64aba370291ae4b932b7.zip
RISC-V: KVM: avoid EBUSY when writing the same isa_ext val
riscv_vcpu_set_isa_ext_single() will prevent any write of isa_ext regs if the vcpu already started spinning. But if there's no extension state (enabled/disabled) made by the userspace, there's no need to -EBUSY out - we can treat the operation as a no-op. zicbom/zicboz_block_size, ISA config reg and mvendorid/march/mimpid already works in a more permissive manner w.r.t userspace writes being a no-op, so let's do the same with isa_ext writes. Signed-off-by: Daniel Henrique Barboza <[email protected]> Reviewed-by: Andrew Jones <[email protected]> Signed-off-by: Anup Patel <[email protected]>
Diffstat (limited to 'arch/riscv/kvm/vcpu_vector.c')
0 files changed, 0 insertions, 0 deletions