qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: Serhii Popovych <spopovyc@redhat.com>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	bharata@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH for 2.13 0/2] target/ppc: Support adding memory to initially memory-less NUMA nodes
Date: Tue, 10 Apr 2018 14:24:32 +1000	[thread overview]
Message-ID: <20180410042432.GI3361@umbus.fritz.box> (raw)
In-Reply-To: <20180406102136.57efebb1@bahia.lan>

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

On Fri, Apr 06, 2018 at 10:21:36AM +0200, Greg Kurz wrote:
> On Thu,  5 Apr 2018 10:35:21 -0400
> Serhii Popovych <spopovyc@redhat.com> wrote:
> 
> > Now PowerPC Linux kernel supports hot-add to NUMA nodes not populated
> > initially with memory we can enable such support in qemu. This requires
> > two changes:
> > 
> >   o Add device tree property "ibm,max-associativity-domains" to let
> >     guest kernel chance to find max possible NUMA node
> > 
> >   o Revert  commit b556854bd852 ("spapr: Don't allow memory hotplug to
> >     memory less nodes") to remove check for hot-add to memory-less node.
> > 
> 
> But the series do the changes in the opposite order... 

Right, the patches should go in the reverse order to avoid breaking
bisections.

> IIUC correctly a recent kernel will mis-behave as before linux commit
> a346137e9142 if the property is not present... ie, patch 2 should come
> first.
> 
> > See description messges for individual changes for more details.
> > 
> > Serhii Popovych (2):
> >   Revert "spapr: Don't allow memory hotplug to memory less nodes"
> >   spapr: Add ibm,max-associativity-domains property
> > 
> >  hw/ppc/spapr.c | 33 +++++++++++----------------------
> >  1 file changed, 11 insertions(+), 22 deletions(-)
> > 
> 

-- 
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: 833 bytes --]

      reply	other threads:[~2018-04-10  4:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 14:35 [Qemu-devel] [PATCH for 2.13 0/2] target/ppc: Support adding memory to initially memory-less NUMA nodes Serhii Popovych
2018-04-05 14:35 ` [Qemu-devel] [PATCH for 2.13 1/2] Revert "spapr: Don't allow memory hotplug to memory less nodes" Serhii Popovych
2018-04-06  3:58   ` Bharata B Rao
2018-04-06  5:48     ` Serhii Popovych
2018-04-10  4:23       ` David Gibson
2018-04-05 14:35 ` [Qemu-devel] [PATCH for 2.13 2/2] spapr: Add ibm, max-associativity-domains property Serhii Popovych
2018-04-10  4:29   ` David Gibson
2018-04-06  8:21 ` [Qemu-devel] [Qemu-ppc] [PATCH for 2.13 0/2] target/ppc: Support adding memory to initially memory-less NUMA nodes Greg Kurz
2018-04-10  4:24   ` 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=20180410042432.GI3361@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=groug@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=spopovyc@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).