From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, nfont@linux.vnet.ibm.com,
imammedo@redhat.com, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/2] spapr: Memory hot-unplug support
Date: Fri, 27 May 2016 11:32:21 -0500 [thread overview]
Message-ID: <20160527163221.7842.32145@loki> (raw)
In-Reply-To: <57486C5D.1060902@redhat.com>
Quoting Thomas Huth (2016-05-27 10:48:45)
> Hi Bharata,
>
> On 15.03.2016 05:38, Bharata B Rao wrote:
> > This patchset adds memory hot removal support for PowerPC sPAPR.
> > This new version switches to using the proposed "count-indexed" type of
> > hotplug identifier which allows to hot remove a number of LMBs starting
> > with a given DRC index.
> >
> > This count-indexed hotplug identifier isn't yet part of PAPR.
>
> Just for clarification / my understanding: That means we also need a
> modified guest to support this new interface? If yes, did you post such
> patches somewhere else already, too?
No patches posted yet, but hopefully soon. These bits will likely be added
as part of an effort that moves all memory hotplug/unplug into guest
kernel instead of relying on drmgr. Most of the bits for in-kernel
memory hotplug are already upstream, but there's a number of other
requirements in the spec update (like a new hotplug interrupt/queue
instead of re-using EPOW) that need to be addressed as part of the
switchover.
>
> Thomas
>
prev parent reply other threads:[~2016-05-27 16:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 4:38 [Qemu-devel] [RFC PATCH v2 0/2] spapr: Memory hot-unplug support Bharata B Rao
2016-03-15 4:38 ` [Qemu-devel] [RFC PATCH v2 1/2] spapr: Add DRC count indexed hotplug identifier type Bharata B Rao
2016-03-16 1:29 ` David Gibson
2016-03-17 16:03 ` Michael Roth
2016-03-15 4:38 ` [Qemu-devel] [RFC PATCH v2 2/2] spapr: Memory hot-unplug support Bharata B Rao
2016-03-16 1:36 ` David Gibson
2016-03-16 4:41 ` Bharata B Rao
2016-03-16 5:11 ` David Gibson
2016-03-23 3:22 ` David Gibson
2016-03-24 14:15 ` Nathan Fontenot
2016-03-29 4:41 ` David Gibson
2016-04-25 9:20 ` Igor Mammedov
2016-04-26 5:09 ` Bharata B Rao
2016-04-26 7:52 ` Igor Mammedov
2016-04-26 21:03 ` Michael Roth
2016-04-27 6:54 ` Thomas Huth
2016-04-27 13:37 ` Igor Mammedov
2016-04-27 13:59 ` Thomas Huth
2016-04-27 14:34 ` Igor Mammedov
2016-04-27 19:07 ` Michael Roth
2016-04-28 7:55 ` Igor Mammedov
2016-04-27 14:24 ` Bharata B Rao
2016-04-29 3:28 ` David Gibson
2016-04-29 8:42 ` Igor Mammedov
2016-04-29 3:24 ` David Gibson
2016-04-29 6:45 ` Thomas Huth
2016-04-29 6:59 ` Bharata B Rao
2016-04-29 8:22 ` Thomas Huth
2016-04-29 8:30 ` Igor Mammedov
2016-04-29 11:01 ` Thomas Huth
2016-04-29 10:11 ` David Gibson
2016-05-27 15:48 ` [Qemu-devel] [RFC PATCH v2 0/2] " Thomas Huth
2016-05-27 16:32 ` Michael Roth [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=20160527163221.7842.32145@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@redhat.com \
--cc=nfont@linux.vnet.ibm.com \
--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).