diff options
| author | Daniel Henrique Barboza <dbarboza@ventanamicro.com> | 2023-08-03 19:32:57 +0300 |
|---|---|---|
| committer | Anup Patel <anup@brainfault.org> | 2023-08-08 14:55:51 +0300 |
| commit | d57304bbfb742bf744d2cd4dc3a08ce3fbfba787 (patch) | |
| tree | ee7b143bf42a79621e7d42e5c8657862112741a1 /scripts/gdb/linux/proc.py | |
| parent | 432a8b35cc23d3af9c60e9c0d191d7ff737afbdc (diff) | |
| download | linux-d57304bbfb742bf744d2cd4dc3a08ce3fbfba787.tar.xz | |
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: Andrew Jones <ajones@ventanamicro.com>
Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
Signed-off-by: Anup Patel <anup@brainfault.org>
Diffstat (limited to 'scripts/gdb/linux/proc.py')
0 files changed, 0 insertions, 0 deletions