From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, alistair.francis@wdc.com,
bmeng@tinylab.org, liweiwei@iscas.ac.cn,
zhiwei_liu@linux.alibaba.com, palmer@rivosinc.com,
ajones@ventanamicro.com, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 1/2] target/riscv/kvm: improve 'init_multiext_cfg' error msg
Date: Tue, 3 Oct 2023 13:53:32 +0200 [thread overview]
Message-ID: <f20c039c-64cd-8530-ef49-bfaa853adc4a@linaro.org> (raw)
In-Reply-To: <20231003113259.771539-2-dbarboza@ventanamicro.com>
Hi Daniel,
On 3/10/23 13:32, 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
>
> Use "error_setg(&error_fatal, ..." since it'll both print the error and
> do an exit(EXIT_FAILURE) in one single call, allowing us to remove
> error_report() and exit().
>
> Finally, 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 | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/target/riscv/kvm/kvm-cpu.c b/target/riscv/kvm/kvm-cpu.c
> index c6615cb807..847cb2876a 100644
> --- a/target/riscv/kvm/kvm-cpu.c
> +++ b/target/riscv/kvm/kvm-cpu.c
> @@ -791,10 +791,9 @@ static void kvm_riscv_init_multiext_cfg(RISCVCPU *cpu, KVMScratchCPU *kvmcpu)
> multi_ext_cfg->supported = false;
> 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);
> - exit(EXIT_FAILURE);
> + error_setg(&error_fatal, "Unable to read ISA_EXT "
See the documentation added in include/qapi/error.h by commit
10303f04b9 ("error: Improve documentation some more"):
* Please don't error_setg(&error_fatal, ...), use error_report() and
* exit(), because that's more obvious.
> + "KVM register %s, error code: %s",
> + multi_ext_cfg->name, strerrorname_np(errno));
> }
> } else {
> multi_ext_cfg->supported = true;
next prev parent reply other threads:[~2023-10-03 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 11:32 [PATCH 0/2] riscv, kvm: support KVM_GET_REG_LIST Daniel Henrique Barboza
2023-10-03 11:32 ` [PATCH 1/2] target/riscv/kvm: improve 'init_multiext_cfg' error msg Daniel Henrique Barboza
2023-10-03 11:53 ` Philippe Mathieu-Daudé [this message]
2023-10-03 11:32 ` [PATCH 2/2] target/riscv/kvm: support KVM_GET_REG_LIST Daniel Henrique Barboza
2023-10-09 1:14 ` [PATCH 0/2] riscv, kvm: " Alistair Francis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f20c039c-64cd-8530-ef49-bfaa853adc4a@linaro.org \
--to=philmd@linaro.org \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=armbru@redhat.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).