From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Nathan Fontenot <nfont@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com, agraf@suse.de,
qemu-ppc@nongnu.org, tyreld@linux.vnet.ibm.com,
imammedo@redhat.com, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC PATCH v1] spapr: Memory hot-unplug support
Date: Wed, 28 Oct 2015 14:47:44 +0530 [thread overview]
Message-ID: <20151028091744.GD747@in.ibm.com> (raw)
In-Reply-To: <562FD5ED.9050306@linux.vnet.ibm.com>
On Tue, Oct 27, 2015 at 02:52:13PM -0500, Nathan Fontenot wrote:
> On 10/26/2015 04:53 AM, Bharata B Rao wrote:
> > Add support to hot remove pc-dimm memory devices.
> >
> > TODO: In response to memory hot removal operation on a DIMM device,
> > guest kernel might refuse to offline a few LMBs that are part of that device.
> > In such cases, we will have a DIMM device that has some LMBs online and some
> > LMBs offline. To avoid this situation, drmgr could be enhanced to support
> > a command line option that results in removal of all the LMBs or none.
> >
>
> We had discussed an update to drmgr previously that would allow one to specify
> that they wanted to remove a certain number of LMBs starting at a specified drc
> index. I would assume we could incorporate the notion that it is an all or
> nothing request into that.
Right, but since that requires PAPR spec changes, I thought for now we
could add such an option to drmgr and use that from rtas_errd on PowerKVM
to correctly do memory hot unplug. Not feasible ?
Regards,
Bharata.
next prev parent reply other threads:[~2015-10-28 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 9:53 [Qemu-devel] [RFC PATCH v1] spapr: Memory hot-unplug support Bharata B Rao
2015-10-27 19:52 ` Nathan Fontenot
2015-10-28 9:17 ` Bharata B Rao [this message]
2015-11-11 1:36 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2015-11-11 7:20 ` Bharata B Rao
2015-11-12 6:03 ` 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=20151028091744.GD747@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=tyreld@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.