qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
	aik@ozlabs.ru, mdroth@linux.vnet.ibm.com, armbru@redhat.com
Cc: lvivier@redhat.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv3 6/9] pseries: Clean up error handling in spapr_rtas_register()
Date: Mon, 18 Jan 2016 10:20:24 +0100	[thread overview]
Message-ID: <569CAE58.4000705@redhat.com> (raw)
In-Reply-To: <1453091083-13931-7-git-send-email-david@gibson.dropbear.id.au>

On 18.01.2016 05:24, David Gibson wrote:
> The errors detected in this function necessarily indicate bugs in the rest
> of the qemu code, rather than an external or configuration problem.
> 
> So, a simple assert() is more appropriate than any more complex error
> reporting.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
>  hw/ppc/spapr_rtas.c | 12 +++---------
>  1 file changed, 3 insertions(+), 9 deletions(-)
> 
> diff --git a/hw/ppc/spapr_rtas.c b/hw/ppc/spapr_rtas.c
> index 34b12a3..0be52ae 100644
> --- a/hw/ppc/spapr_rtas.c
> +++ b/hw/ppc/spapr_rtas.c
> @@ -648,17 +648,11 @@ target_ulong spapr_rtas_call(PowerPCCPU *cpu, sPAPRMachineState *spapr,
>  
>  void spapr_rtas_register(int token, const char *name, spapr_rtas_fn fn)
>  {
> -    if (!((token >= RTAS_TOKEN_BASE) && (token < RTAS_TOKEN_MAX))) {
> -        fprintf(stderr, "RTAS invalid token 0x%x\n", token);
> -        exit(1);
> -    }
> +    assert((token >= RTAS_TOKEN_BASE) && (token < RTAS_TOKEN_MAX));

While you're at it, you could also get rid of some superfluous
parentheses in that statement:

	assert(token >= RTAS_TOKEN_BASE && token < RTAS_TOKEN_MAX);

>      token -= RTAS_TOKEN_BASE;
> -    if (rtas_table[token].name) {
> -        fprintf(stderr, "RTAS call \"%s\" is registered already as 0x%x\n",
> -                rtas_table[token].name, token);
> -        exit(1);
> -    }
> +
> +    assert(!rtas_table[token].name);
>  
>      rtas_table[token].name = name;
>      rtas_table[token].fn = fn;
> 

Anyway, patch sounds reasonable,
Reviewed-by: Thomas Huth <thuth@redhat.com>

  reply	other threads:[~2016-01-18  9:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  4:24 [Qemu-devel] [PATCHv3 0/9] Cleanups to error reporting on ppc and spapr David Gibson
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 1/9] ppc: Cleanup error handling in ppc_set_compat() David Gibson
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 2/9] pseries: Cleanup error handling of spapr_cpu_init() David Gibson
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 3/9] pseries: Clean up hash page table allocation error handling David Gibson
2016-01-18  8:47   ` Thomas Huth
2016-01-18 10:21     ` Markus Armbruster
2016-01-19  1:12       ` David Gibson
2016-01-19  0:20     ` David Gibson
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 4/9] pseries: Clean up error handling in spapr_validate_node_memory() David Gibson
2016-01-18  9:15   ` Thomas Huth
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 5/9] pseries: Cleanup error handling in spapr_vga_init() David Gibson
2016-01-18  9:16   ` Thomas Huth
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 6/9] pseries: Clean up error handling in spapr_rtas_register() David Gibson
2016-01-18  9:20   ` Thomas Huth [this message]
2016-01-19  0:23     ` David Gibson
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 7/9] pseries: Clean up error handling in xics_system_init() David Gibson
2016-01-18  9:25   ` Thomas Huth
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 8/9] pseries: Clean up error reporting in ppc_spapr_init() David Gibson
2016-01-18  9:31   ` Thomas Huth
2016-01-18 10:06     ` Markus Armbruster
2016-01-19  1:23     ` David Gibson
2016-01-18  4:24 ` [Qemu-devel] [PATCHv3 9/9] pseries: Clean up error reporting in htab migration functions 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=569CAE58.4000705@redhat.com \
    --to=thuth@redhat.com \
    --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).