All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: aik@ozlabs.ru, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Don't create ibm, dynamic-reconfiguration-memory w/o DR LMBs
Date: Wed, 20 Jan 2016 11:00:39 +0530	[thread overview]
Message-ID: <20160120053039.GA18882@in.ibm.com> (raw)
In-Reply-To: <20160119050025.GB27454@voom.redhat.com>

On Tue, Jan 19, 2016 at 04:00:25PM +1100, David Gibson wrote:
> On Tue, Jan 19, 2016 at 10:09:21AM +0530, Bharata B Rao wrote:
> > If guest doesn't have any dynamically reconfigurable (DR) logical memory
> > blocks (LMB), then we shouldn't create ibm,dynamic-reconfiguration-memory
> > device tree node.
> > 
> > Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> > ---
> > This applies against ppc-for-2.6 branch of David Gibson's tree.
> 
> Applied to ppc-for-2.6, thanks.

There is a slight change in memory nodes representation in DT after this fix
that could result in the following behaviour before and after migration.

For a guest with -m 4G -numa node,nodeid=0,mem=2G -numa node,nodeid=1,mem=2G,
the DT under /proc/device-tree changes like this:

Guest started with QEMU w/o this fix
------------------------------------
memory@0
memory@80000000
ibm,dynamic-reconfiguration-memory

Guest migrated to QEMU w/ this fix included
-------------------------------------------
memory@0
memory@80000000
ibm,dynamic-reconfiguration-memory

After next reboot
-----------------
memory@0
memory@80000000

I guess this is ok, but wanted to sound out this change explicitly.

Regards,
Bharata.

  reply	other threads:[~2016-01-20  5:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19  4:39 [Qemu-devel] [PATCH] spapr: Don't create ibm, dynamic-reconfiguration-memory w/o DR LMBs Bharata B Rao
2016-01-19  5:00 ` David Gibson
2016-01-20  5:30   ` Bharata B Rao [this message]
2016-01-21  1:13     ` 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=20160120053039.GA18882@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --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 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.