RISC-V: KVM: avoid EBUSY when writing the same isa_ext val
authorDaniel Henrique Barboza <dbarboza@ventanamicro.com>
Thu, 3 Aug 2023 16:33:00 +0000 (13:33 -0300)
committerAnup Patel <anup@brainfault.org>
Tue, 8 Aug 2023 11:55:58 +0000 (17:25 +0530)
commit1099c80906d358db542c64aba370291ae4b932b7
treefe6a1519846b8bfeb703a9247601ac07e342193d
parent63bd660657efade03270c8cc7e3d9b6993350e56
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 <dbarboza@ventanamicro.com>
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
Signed-off-by: Anup Patel <anup@brainfault.org>
arch/riscv/kvm/vcpu_onereg.c