Commit d57304bb authored by Daniel Henrique Barboza's avatar Daniel Henrique Barboza Committed by Anup Patel
Browse files

RISC-V: KVM: use EBUSY when !vcpu->arch.ran_atleast_once 



vcpu_set_reg_config() and vcpu_set_reg_isa_ext() is throwing an
EOPNOTSUPP error when !vcpu->arch.ran_atleast_once. In similar cases
we're throwing an EBUSY error, like in mvendorid/marchid/mimpid
set_reg().

EOPNOTSUPP has a conotation of finality. EBUSY is more adequate in this
case since its a condition/error related to the vcpu lifecycle.

Change these EOPNOTSUPP instances to EBUSY.

Suggested-by: default avatarAndrew Jones <ajones@ventanamicro.com>
Signed-off-by: default avatarDaniel Henrique Barboza <dbarboza@ventanamicro.com>
Reviewed-by: default avatarAndrew Jones <ajones@ventanamicro.com>
Signed-off-by: default avatarAnup Patel <anup@brainfault.org>
parent 432a8b35

arch/riscv/kvm/vcpu_onereg.c

+2 −2
Original line number Diff line number Diff line
@@ -212,7 +212,7 @@ static int kvm_riscv_vcpu_set_reg_config(struct kvm_vcpu *vcpu, 
			vcpu->arch.isa[0] = reg_val;

			kvm_riscv_vcpu_fp_reset(vcpu);

		} else {

			return -EOPNOTSUPP;

			return -EBUSY;

		}

		break;

	case KVM_REG_RISCV_CONFIG_REG(zicbom_block_size):
@@ -484,7 +484,7 @@ static int riscv_vcpu_set_isa_ext_single(struct kvm_vcpu *vcpu, 
			return -EINVAL;

		kvm_riscv_vcpu_fp_reset(vcpu);

	} else {

		return -EOPNOTSUPP;

		return -EBUSY;

	}



	return 0;