From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: agraf@suse.de, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 2/2] hw/ppc/spapr: Use error_report() instead of hw_error()
Date: Thu, 30 Apr 2015 13:32:05 +1000 [thread overview]
Message-ID: <5541A235.8060407@ozlabs.ru> (raw)
In-Reply-To: <1430334068-12772-3-git-send-email-thuth@redhat.com>
On 04/30/2015 05:01 AM, Thomas Huth wrote:
> hw_error() is designed for printing CPU-related error messages
> (e.g. it also prints a full CPU register dump). For error messages
> that are not directly related to CPU problems, a function like
> error_report() should be used instead.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> hw/ppc/spapr.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index 226f029..92b1c0b 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -794,8 +794,8 @@ static void spapr_finalize_fdt(sPAPREnvironment *spapr,
> _FDT((fdt_pack(fdt)));
>
> if (fdt_totalsize(fdt) > FDT_MAX_SIZE) {
> - hw_error("FDT too big ! 0x%x bytes (max is 0x%x)\n",
> - fdt_totalsize(fdt), FDT_MAX_SIZE);
> + error_report("FDT too big ! 0x%x bytes (max is 0x%x)",
> + fdt_totalsize(fdt), FDT_MAX_SIZE);
You did adjust indent here...
> exit(1);
> }
>
> @@ -1419,7 +1419,7 @@ static void ppc_spapr_init(MachineState *machine)
> rma_alloc_size = kvmppc_alloc_rma(&rma);
>
> if (rma_alloc_size == -1) {
> - hw_error("qemu: Unable to create RMA\n");
> + error_report("Unable to create RMA");
> exit(1);
> }
>
> @@ -1520,17 +1520,17 @@ static void ppc_spapr_init(MachineState *machine)
>
> filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, "spapr-rtas.bin");
> if (!filename) {
> - hw_error("Could not find LPAR rtas '%s'\n", "spapr-rtas.bin");
> + error_report("Could not find LPAR rtas '%s'", "spapr-rtas.bin");
> exit(1);
> }
> spapr->rtas_size = get_image_size(filename);
> spapr->rtas_blob = g_malloc(spapr->rtas_size);
> if (load_image_size(filename, spapr->rtas_blob, spapr->rtas_size) < 0) {
> - hw_error("qemu: could not load LPAR rtas '%s'\n", filename);
> + error_report("Could not load LPAR rtas '%s'", filename);
> exit(1);
> }
> if (spapr->rtas_size > RTAS_MAX_SIZE) {
> - hw_error("RTAS too big ! 0x%zx bytes (max is 0x%x)\n",
> + error_report("RTAS too big ! 0x%zx bytes (max is 0x%x)",
> (size_t)spapr->rtas_size, RTAS_MAX_SIZE);
... but not here :)
> exit(1);
> }
>
--
Alexey
next prev parent reply other threads:[~2015-04-30 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 19:01 [Qemu-devel] [PATCH 0/2] hw/ppc/spapr: Improve error printing Thomas Huth
2015-04-29 19:01 ` [Qemu-devel] [PATCH 1/2] hw/ppc/spapr: Fix error message when firmware could not be loaded Thomas Huth
2015-04-29 19:01 ` [Qemu-devel] [PATCH 2/2] hw/ppc/spapr: Use error_report() instead of hw_error() Thomas Huth
2015-04-30 3:32 ` Alexey Kardashevskiy [this message]
2015-04-30 17:03 ` Thomas Huth
2015-05-01 3:42 ` David Gibson
2015-04-30 1:02 ` [Qemu-devel] [PATCH 0/2] hw/ppc/spapr: Improve error printing 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=5541A235.8060407@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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).