diff options
| author |   Daniel Henrique Barboza <dbarboza@ventanamicro.com> | 2023-08-03 13:32:57 -0300 |
|---|---|---|
| committer |   Anup Patel <anup@brainfault.org> | 2023-08-08 17:25:51 +0530 |
| commit | d57304bbfb742bf744d2cd4dc3a08ce3fbfba787 (patch) | |
| tree | ee7b143bf42a79621e7d42e5c8657862112741a1 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | RISC-V: KVM: do not EOPNOTSUPP in set KVM_REG_RISCV_TIMER_REG (diff) | |
| download | wireguard-linux-d57304bbfb742bf744d2cd4dc3a08ce3fbfba787.tar.xz wireguard-linux-d57304bbfb742bf744d2cd4dc3a08ce3fbfba787.zip | |
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 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions