From: Greg Kurz <groug@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Serhii Popovych <spopovyc@redhat.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH for 2.13] spapr: Correct max associativity domains value for non-NUMA configs
Date: Wed, 18 Apr 2018 11:45:46 +0200 [thread overview]
Message-ID: <20180418110902.50ec50a3@bahia.lan> (raw)
In-Reply-To: <20180418014908.GE2317@umbus.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]
On Wed, 18 Apr 2018 11:49:08 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Tue, Apr 17, 2018 at 07:17:51PM +0200, Greg Kurz wrote:
> > Cc'ing David who should always be in the recipient list when posting ppc related
> > patches :)
> >
> > On Tue, 17 Apr 2018 12:21:35 -0400
> > Serhii Popovych <spopovyc@redhat.com> wrote:
> >
> > > In non-NUMA configurations nb_numa_nodes is zero and we set 5th cell
> > > in ibm,max-associativity-domains to -1. That causes to stall Linux
> > > guests during boot after following line:
> > >
> > > [ 0.000000] NUMA associativity depth for CPU/Memory: 4
> > >
> > > Make last possible NUMA in property zero to correct support for
> > > non-NUMA guests.
> > >
> >
> > Alternatively, as suggested by David in some other mail, you could drop the
> > property in this case. I've checked it fixes the hang too, and it probably
> > makes more sense than exposing only zeroes.
>
> Actually, I think this is the better solution. qemu treats "not NUMA"
> and "exactly one NUMA node" differently for historical reasons, but I
> don't think that actually makes a whole lot of sense. I think
> advertising them identically so we don't generate more special cases
> on the guest side is a better idea.
>
Fair enough. Thanks for the explanation.
> > > Fixes: c1df49a670ef ("spapr: Add ibm,max-associativity-domains property")
> >
> > Since c1df49a670ef hasn't hit master yet, I guess we should squash this
> > patch (or any alternative) there to preserve bisect, ie, either David
> > does it for you or you post a v4 of your previous series.
>
> Right, I've folded these together in my tree so we don't get an
> interval of broken commits.
>
> >
> > > Signed-off-by: Serhii Popovych <spopovyc@redhat.com>
> > > ---
> > > hw/ppc/spapr.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> > > index 7b2bc4e..bff2125 100644
> > > --- a/hw/ppc/spapr.c
> > > +++ b/hw/ppc/spapr.c
> > > @@ -914,7 +914,7 @@ static void spapr_dt_rtas(sPAPRMachineState *spapr, void *fdt)
> > > cpu_to_be32(0),
> > > cpu_to_be32(0),
> > > cpu_to_be32(0),
> > > - cpu_to_be32(nb_numa_nodes - 1),
> > > + cpu_to_be32(nb_numa_nodes ? nb_numa_nodes - 1 : 0),
> > > };
> > >
> > > _FDT(rtas = fdt_add_subnode(fdt, 0, "rtas"));
> >
> >
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-04-18 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 16:21 [Qemu-devel] [PATCH for 2.13] spapr: Correct max associativity domains value for non-NUMA configs Serhii Popovych
2018-04-17 17:17 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2018-04-18 1:49 ` David Gibson
2018-04-18 9:45 ` Greg Kurz [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=20180418110902.50ec50a3@bahia.lan \
--to=groug@kaod.org \
--cc=david@gibson.dropbear.id.au \
--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).