qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, 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 14:55:15 +1000	[thread overview]
Message-ID: <20160426045515.GI15176@voom.fritz.box> (raw)
In-Reply-To: <20160426035053.GA9793@in.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

On Tue, Apr 26, 2016 at 09:20:53AM +0530, Bharata B Rao wrote:
> On Tue, Apr 26, 2016 at 11:18:25AM +1000, David Gibson wrote:
> > 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.
> 
> Checked that memory hotplug is working fine after this fix. So if it
> matters now,
> 
> Tested-by: Bharata B Rao <bharata@linux.vnet.ibm.com>

Thanks, but I already sent the pull request.

-- 
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 --]

      reply	other threads:[~2016-04-26  5:01 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
2016-04-26  3:50   ` Bharata B Rao
2016-04-26  4:55     ` David Gibson [this message]

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=20160426045515.GI15176@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).