From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
armbru@redhat.com, aik@ozlabs.ru, mdroth@linux.vnet.ibm.com
Cc: lvivier@redhat.com, qemu-ppc@nongnu.org, agraf@suse.de,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 07/11] pseries: Cleanup error handling in spapr_kvm_type()
Date: Fri, 11 Dec 2015 11:01:37 +0100 [thread overview]
Message-ID: <566A9F01.7090203@redhat.com> (raw)
In-Reply-To: <1449792685-17000-8-git-send-email-david@gibson.dropbear.id.au>
On 11/12/15 01:11, David Gibson wrote:
> Use error_setg() and &error_fatal instead of an explicit exit().
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> hw/ppc/spapr.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index fd16db4..546d2f5 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -2035,8 +2035,8 @@ static int spapr_kvm_type(const char *vm_type)
> return 2;
> }
>
> - error_report("Unknown kvm-type specified '%s'", vm_type);
> - exit(1);
> + error_setg(&error_fatal, "Unknown kvm-type specified '%s'", vm_type);
> + return 0;
> }
Honestly, I'd rather prefer the original code here. error_setg() should
IMHO be used to set an error in an "flexible" error variable. Using it
with an "hard-coded" error_fatal sounds ugly to me. And as far as I can
see, no other code in QEMU uses error_setg(&error_fatal, ...) - so we
should maybe not start with this in the spapr code as well.
If you still would like to get rid of the exit() here ... maybe you
could introduce some kind of error_report_fatal() function instead that
exits after reporting the error with error_report() ?
Thomas
next prev parent reply other threads:[~2015-12-11 10:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 0:11 [Qemu-devel] [PATCH 00/11] Error handling cleanups for pseries machine type David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 01/11] ppc: Cleanup error handling in ppc_set_compat() David Gibson
2015-12-11 9:17 ` Thomas Huth
2015-12-11 13:58 ` Eric Blake
2015-12-14 0:54 ` David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 02/11] pseries: Cleanup error handling of spapr_cpu_init() David Gibson
2015-12-11 8:45 ` Bharata B Rao
2015-12-14 1:01 ` David Gibson
2015-12-11 14:54 ` Eric Blake
2015-12-14 1:04 ` David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 03/11] pseries: Clean up hash page table allocation error handling David Gibson
2015-12-11 8:40 ` Bharata B Rao
2015-12-14 1:11 ` David Gibson
2015-12-11 15:01 ` Eric Blake
2015-12-14 1:11 ` David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 04/11] pseries: Clean up error handling in spapr_validate_node_memory() David Gibson
2015-12-11 8:56 ` Bharata B Rao
2015-12-11 0:11 ` [Qemu-devel] [PATCH 05/11] pseries: Cleanup error handling in spapr_vga_init() David Gibson
2015-12-11 9:35 ` Thomas Huth
2015-12-14 1:13 ` David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 06/11] pseries: Improve error handling in find_unknown_sysbus_device() David Gibson
2015-12-11 9:49 ` Thomas Huth
2015-12-14 1:20 ` David Gibson
2015-12-11 15:15 ` Eric Blake
2015-12-14 1:21 ` David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 07/11] pseries: Cleanup error handling in spapr_kvm_type() David Gibson
2015-12-11 10:01 ` Thomas Huth [this message]
2015-12-14 1:24 ` David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 08/11] pseries: Clean up error handling in spapr_rtas_register() David Gibson
2015-12-11 10:06 ` Thomas Huth
2015-12-11 0:11 ` [Qemu-devel] [PATCH 09/11] pseries: Clean up error handling in xics_system_init() David Gibson
2015-12-11 10:08 ` Thomas Huth
2015-12-14 1:26 ` David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 10/11] pseries: Clean up error handling in ppc_spapr_init() David Gibson
2015-12-11 0:11 ` [Qemu-devel] [PATCH 11/11] pseries: Clean up error reporting in htab migration functions David Gibson
2015-12-11 10:12 ` Thomas Huth
2015-12-11 15:22 ` Eric Blake
2015-12-14 1:28 ` David Gibson
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=566A9F01.7090203@redhat.com \
--to=thuth@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).