From: David Gibson <david@gibson.dropbear.id.au>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, Bharata B Rao <bharata@linux.vnet.ibm.com>,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.6] spapr_drc: fix aborts during DRC-count based hotplug
Date: Tue, 26 Apr 2016 11:18:25 +1000 [thread overview]
Message-ID: <20160426011825.GG15176@voom.fritz.box> (raw)
In-Reply-To: <1461623065-6621-1-git-send-email-mdroth@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 4001 bytes --]
On Mon, Apr 25, 2016 at 05:24:25PM -0500, Michael Roth wrote:
> CPU/memory resources can be signalled en-masse via
> spapr_hotplug_req_add_by_count(), and when doing so, actually change
> the meaning of the 'drc' parameter passed to
> spapr_hotplug_req_event() to be a count rather than an index.
>
> f40eb92 added a hook in spapr_hotplug_req_event() to record when a
> device had been 'signalled' to the guest, but that code assumes that
> drc is always an index. In cases where it's a count, such as memory
> hotplug, the DRC lookup will fail, leading to an assert.
>
> Fix this by only explicitly setting the signalled state for cases where
> we are doing PCI hotplug.
>
> For other resources types, since we cannot selectively track whether a
> resource has been signalled in cases where we signal attach as a count,
> set the 'signalled' state to true immediately upon making the
> resource available via drck->attach().
>
> Reported-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> Cc: Bharata B Rao <bharata@linux.vnet.ibm.com>
> Cc: david@gibson.dropbear.id.au
> Cc: qemu-ppc@nongnu.org
> Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Applued to 2.6, I'll send a pull request today.
> ---
> Really sorry for the way last-minute fix, but without this memory hotplug
> is totally broken :( Hoping to get this in for Wednesday's RC4, which
> I think will be the final before release.
> ---
> hw/ppc/spapr_drc.c | 12 +++++++++++-
> hw/ppc/spapr_events.c | 7 +++----
> 2 files changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/hw/ppc/spapr_drc.c b/hw/ppc/spapr_drc.c
> index 3173940..1f5f1d7 100644
> --- a/hw/ppc/spapr_drc.c
> +++ b/hw/ppc/spapr_drc.c
> @@ -364,7 +364,17 @@ static void attach(sPAPRDRConnector *drc, DeviceState *d, void *fdt,
> drc->fdt = fdt;
> drc->fdt_start_offset = fdt_start_offset;
> drc->configured = coldplug;
> - drc->signalled = coldplug;
> + /* 'logical' DR resources such as memory/cpus are in some cases treated
> + * as a pool of resources from which the guest is free to choose from
> + * based on only a count. for resources that can be assigned in this
> + * fashion, we must assume the resource is signalled immediately
> + * since a single hotplug request might make an arbitrary number of
> + * such attached resources available to the guest, as opposed to
> + * 'physical' DR resources such as PCI where each device/resource is
> + * signalled individually.
> + */
> + drc->signalled = (drc->type != SPAPR_DR_CONNECTOR_TYPE_PCI)
> + ? true : coldplug;
>
> object_property_add_link(OBJECT(drc), "device",
> object_get_typename(OBJECT(drc->dev)),
> diff --git a/hw/ppc/spapr_events.c b/hw/ppc/spapr_events.c
> index 269ab7e..049fb1b 100644
> --- a/hw/ppc/spapr_events.c
> +++ b/hw/ppc/spapr_events.c
> @@ -442,6 +442,9 @@ static void spapr_hotplug_req_event(uint8_t hp_id, uint8_t hp_action,
> switch (drc_type) {
> case SPAPR_DR_CONNECTOR_TYPE_PCI:
> hp->hotplug_type = RTAS_LOG_V6_HP_TYPE_PCI;
> + if (hp->hotplug_action == RTAS_LOG_V6_HP_ACTION_ADD) {
> + spapr_hotplug_set_signalled(drc);
> + }
> break;
> case SPAPR_DR_CONNECTOR_TYPE_LMB:
> hp->hotplug_type = RTAS_LOG_V6_HP_TYPE_MEMORY;
> @@ -462,10 +465,6 @@ static void spapr_hotplug_req_event(uint8_t hp_id, uint8_t hp_action,
>
> rtas_event_log_queue(RTAS_LOG_TYPE_HOTPLUG, new_hp, true);
>
> - if (hp->hotplug_action == RTAS_LOG_V6_HP_ACTION_ADD) {
> - spapr_hotplug_set_signalled(drc);
> - }
> -
> qemu_irq_pulse(xics_get_qirq(spapr->icp, spapr->check_exception_irq));
> }
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-26 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 22:24 [Qemu-devel] [PATCH for-2.6] spapr_drc: fix aborts during DRC-count based hotplug Michael Roth
2016-04-26 1:18 ` David Gibson [this message]
2016-04-26 3:50 ` Bharata B Rao
2016-04-26 4:55 ` 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=20160426011825.GG15176@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=bharata@linux.vnet.ibm.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).