From: "Cédric Le Goater" <clg@kaod.org>
To: Greg Kurz <groug@kaod.org>, David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH for-5.0 4/4] spapr: Abort if XICS interrupt controller cannot be initialized
Date: Mon, 18 Nov 2019 09:07:10 +0100 [thread overview]
Message-ID: <cb43b24e-182f-195b-a626-d5a48b16d708@kaod.org> (raw)
In-Reply-To: <157403285265.409804.8683093665795248192.stgit@bahia.lan>
On 18/11/2019 00:20, Greg Kurz wrote:
> Failing to set any of the ICS property should really never happen:
> - object_property_add_child() always succeed unless the child object
> already has a parent, which isn't the case here obviously since the
> ICS has just been created with object_new()
> - the ICS has an "nr-irqs" property than can be set as long as the ICS
> isn't realized
>
> In both cases, an error indicates there is a bug in QEMU. Propagating the
> error, ie. exiting QEMU since spapr_irq_init() is called with &error_fatal
> doesn't make much sense. Abort instead. This is consistent with what is
> done with XIVE : both qdev_create() and qdev_prop_set_uint32() abort QEMU
> on error.
>
> Signed-off-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Thanks,
C.
> ---
> hw/ppc/spapr_irq.c | 13 ++-----------
> 1 file changed, 2 insertions(+), 11 deletions(-)
>
> diff --git a/hw/ppc/spapr_irq.c b/hw/ppc/spapr_irq.c
> index 487c8ceb35a3..37f65dac9ca8 100644
> --- a/hw/ppc/spapr_irq.c
> +++ b/hw/ppc/spapr_irq.c
> @@ -313,20 +313,11 @@ void spapr_irq_init(SpaprMachineState *spapr, Error **errp)
> Object *obj;
>
> obj = object_new(TYPE_ICS_SPAPR);
> - object_property_add_child(OBJECT(spapr), "ics", obj, &local_err);
> - if (local_err) {
> - error_propagate(errp, local_err);
> - return;
> - }
>
> + object_property_add_child(OBJECT(spapr), "ics", obj, &error_abort);
> object_property_set_link(obj, OBJECT(spapr), ICS_PROP_XICS,
> &error_abort);
> - object_property_set_int(obj, smc->nr_xirqs, "nr-irqs", &local_err);
> - if (local_err) {
> - error_propagate(errp, local_err);
> - return;
> - }
> -
> + object_property_set_int(obj, smc->nr_xirqs, "nr-irqs", &error_abort);
> object_property_set_bool(obj, true, "realized", &local_err);
> if (local_err) {
> error_propagate(errp, local_err);
>
next prev parent reply other threads:[~2019-11-18 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 23:20 [PATCH for-5.0 0/4] ppc: Some more QOM cleanup for XICS Greg Kurz
2019-11-17 23:20 ` [PATCH for-5.0 1/4] xics: Link ICS_PROP_XICS property to ICSState::xics pointer Greg Kurz
2019-11-18 8:03 ` Cédric Le Goater
2019-11-17 23:20 ` [PATCH for-5.0 2/4] xics: Link ICP_PROP_XICS property to ICPState::xics pointer Greg Kurz
2019-11-18 8:03 ` Cédric Le Goater
2019-11-17 23:20 ` [PATCH for-5.0 3/4] xics: Link ICP_PROP_CPU property to ICPState::cs pointer Greg Kurz
2019-11-18 8:04 ` Cédric Le Goater
2019-11-17 23:20 ` [PATCH for-5.0 4/4] spapr: Abort if XICS interrupt controller cannot be initialized Greg Kurz
2019-11-18 8:07 ` Cédric Le Goater [this message]
2019-11-19 0:37 ` [PATCH for-5.0 0/4] ppc: Some more QOM cleanup for XICS 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=cb43b24e-182f-195b-a626-d5a48b16d708@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--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).