Message ID | 20231003132148.797921-2-dbarboza@ventanamicro.com |
---|---|
State | New |
Headers | show |
Series | riscv, kvm: support KVM_GET_REG_LIST | expand |
On 3/10/23 15:21, Daniel Henrique Barboza wrote: > Our error message is returning the value of 'ret', which will be always > -1 in case of error, and will not be that useful: > > qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error -1 > > Improve the error message by outputting 'errno' instead of 'ret'. Use > strerrorname_np() to output the error name instead of the error code. > This will give us what we need to know right away: > > qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error code: ENOENT > > Given that we're going to exit(1) in this condition instead of > attempting to recover, remove the 'kvm_riscv_destroy_scratch_vcpu()' > call. > > Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> > --- > target/riscv/kvm/kvm-cpu.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
On Tue, Oct 03, 2023 at 10:21:47AM -0300, Daniel Henrique Barboza wrote: > Our error message is returning the value of 'ret', which will be always > -1 in case of error, and will not be that useful: > > qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error -1 > > Improve the error message by outputting 'errno' instead of 'ret'. Use > strerrorname_np() to output the error name instead of the error code. > This will give us what we need to know right away: > > qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error code: ENOENT > > Given that we're going to exit(1) in this condition instead of > attempting to recover, remove the 'kvm_riscv_destroy_scratch_vcpu()' > call. > > Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> > --- > target/riscv/kvm/kvm-cpu.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/target/riscv/kvm/kvm-cpu.c b/target/riscv/kvm/kvm-cpu.c > index c6615cb807..c3daf74fe9 100644 > --- a/target/riscv/kvm/kvm-cpu.c > +++ b/target/riscv/kvm/kvm-cpu.c > @@ -792,8 +792,8 @@ static void kvm_riscv_init_multiext_cfg(RISCVCPU *cpu, KVMScratchCPU *kvmcpu) > val = false; > } else { > error_report("Unable to read ISA_EXT KVM register %s, " > - "error %d", multi_ext_cfg->name, ret); > - kvm_riscv_destroy_scratch_vcpu(kvmcpu); > + "error code: %s", multi_ext_cfg->name, > + strerrorname_np(errno)); > exit(EXIT_FAILURE); > } > } else { > -- > 2.41.0 > Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
On Wed, Oct 4, 2023 at 12:46 AM Daniel Henrique Barboza <dbarboza@ventanamicro.com> wrote: > > Our error message is returning the value of 'ret', which will be always > -1 in case of error, and will not be that useful: > > qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error -1 > > Improve the error message by outputting 'errno' instead of 'ret'. Use > strerrorname_np() to output the error name instead of the error code. > This will give us what we need to know right away: > > qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error code: ENOENT > > Given that we're going to exit(1) in this condition instead of > attempting to recover, remove the 'kvm_riscv_destroy_scratch_vcpu()' > call. > > Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> Reviewed-by: Alistair Francis <alistair.francis@wdc.com> Alistair > --- > target/riscv/kvm/kvm-cpu.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/target/riscv/kvm/kvm-cpu.c b/target/riscv/kvm/kvm-cpu.c > index c6615cb807..c3daf74fe9 100644 > --- a/target/riscv/kvm/kvm-cpu.c > +++ b/target/riscv/kvm/kvm-cpu.c > @@ -792,8 +792,8 @@ static void kvm_riscv_init_multiext_cfg(RISCVCPU *cpu, KVMScratchCPU *kvmcpu) > val = false; > } else { > error_report("Unable to read ISA_EXT KVM register %s, " > - "error %d", multi_ext_cfg->name, ret); > - kvm_riscv_destroy_scratch_vcpu(kvmcpu); > + "error code: %s", multi_ext_cfg->name, > + strerrorname_np(errno)); > exit(EXIT_FAILURE); > } > } else { > -- > 2.41.0 > >
diff --git a/target/riscv/kvm/kvm-cpu.c b/target/riscv/kvm/kvm-cpu.c index c6615cb807..c3daf74fe9 100644 --- a/target/riscv/kvm/kvm-cpu.c +++ b/target/riscv/kvm/kvm-cpu.c @@ -792,8 +792,8 @@ static void kvm_riscv_init_multiext_cfg(RISCVCPU *cpu, KVMScratchCPU *kvmcpu) val = false; } else { error_report("Unable to read ISA_EXT KVM register %s, " - "error %d", multi_ext_cfg->name, ret); - kvm_riscv_destroy_scratch_vcpu(kvmcpu); + "error code: %s", multi_ext_cfg->name, + strerrorname_np(errno)); exit(EXIT_FAILURE); } } else {
Our error message is returning the value of 'ret', which will be always -1 in case of error, and will not be that useful: qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error -1 Improve the error message by outputting 'errno' instead of 'ret'. Use strerrorname_np() to output the error name instead of the error code. This will give us what we need to know right away: qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error code: ENOENT Given that we're going to exit(1) in this condition instead of attempting to recover, remove the 'kvm_riscv_destroy_scratch_vcpu()' call. Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> --- target/riscv/kvm/kvm-cpu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)