qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aditya Gupta <adityag@linux.ibm.com>
To: Vishal Chourasia <vishalc@linux.ibm.com>
Cc: harshpb@linux.ibm.com, milesg@linux.ibm.com, npiggin@gmail.com,
	peter.maydell@linaro.org, alistair23@gmail.com,
	balaton@eik.bme.hu, qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	berrange@redhat.com, hpoussin@reactos.org
Subject: Re: [Patch v7 5/5] hw/ppc: Pass errp to load_image_targphys() and report errors
Date: Fri, 24 Oct 2025 08:58:30 +0530	[thread overview]
Message-ID: <cc23968d-9a17-43b5-80ef-0da8f8f782c2@linux.ibm.com> (raw)
In-Reply-To: <20251022192717.1644251-11-vishalc@linux.ibm.com>

On 23/10/25 00:57, Vishal Chourasia wrote:

> Pass errp to load_image_targphys() calls in ppc machine initialization
> to capture detailed error information when loading firmware, kernel,
> and initrd images.
>
> Pass error_fatal which automatically reports detailed error messages and
> exits immediately on failure. Eliminating redundant exit(1) calls, as
> error_fatal handles termination

Nitpick: There's no 'errp' now and we aren't capturing error info in 
caller anymore, can replace that with error_fatal.


The patch looks good to me. Will test.


Thanks,

- Aditya G


> The behavior remains functionally identical, but error messages now
> come directly from the loader function with more context about the
> failure cause.
>
> Signed-off-by: Vishal Chourasia <vishalc@linux.ibm.com>
> ---
>   hw/ppc/amigaone.c      | 13 ++-----------
>   hw/ppc/e500.c          | 19 +++----------------
>   hw/ppc/mac_newworld.c  | 16 +++-------------
>   hw/ppc/mac_oldworld.c  | 16 +++-------------
>   hw/ppc/pegasos2.c      |  9 ++-------
>   hw/ppc/pnv.c           | 28 +++++-----------------------
>   hw/ppc/ppc440_bamboo.c |  8 +-------
>   hw/ppc/prep.c          | 17 ++++-------------
>   hw/ppc/sam460ex.c      |  7 +------
>   hw/ppc/spapr.c         | 13 ++-----------
>   hw/ppc/virtex_ml507.c  | 10 ++--------
>   11 files changed, 28 insertions(+), 128 deletions(-)


  reply	other threads:[~2025-10-24  3:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 19:27 [Patch v7 0/5] hw/core/loader: capture Error from load_image_targphys Vishal Chourasia
2025-10-22 19:27 ` [Patch v7 1/5] hw/core/loader: Use qemu_open() instead of open() in get_image_size() Vishal Chourasia
2025-10-22 19:27 ` [Patch v7 2/5] hw/core/loader: capture Error from load_image_targphys Vishal Chourasia
2025-10-24  3:19   ` Aditya Gupta
2025-10-22 19:27 ` [Patch v7 3/5] hw/core/loader: add check for zero size in load_image_targphys_as Vishal Chourasia
2025-10-22 19:27 ` [Patch v7 4/5] hw/core: Pass errp to load_image_targphys_as() Vishal Chourasia
2025-10-22 19:27 ` [Patch v7 5/5] hw/ppc: Pass errp to load_image_targphys() and report errors Vishal Chourasia
2025-10-24  3:28   ` Aditya Gupta [this message]
2025-10-23 14:08 ` [Patch v7 0/5] hw/core/loader: capture Error from load_image_targphys Vishal Chourasia

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=cc23968d-9a17-43b5-80ef-0da8f8f782c2@linux.ibm.com \
    --to=adityag@linux.ibm.com \
    --cc=alistair23@gmail.com \
    --cc=balaton@eik.bme.hu \
    --cc=berrange@redhat.com \
    --cc=harshpb@linux.ibm.com \
    --cc=hpoussin@reactos.org \
    --cc=milesg@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=vishalc@linux.ibm.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).