From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
qemu-ppc@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] pseries: do not allow memory-less/cpu-less NUMA node
Date: Mon, 2 Sep 2019 16:27:18 +1000 [thread overview]
Message-ID: <20190902062718.GG415@umbus.fritz.box> (raw)
In-Reply-To: <20190830194543.6c1f5776@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]
On Fri, Aug 30, 2019 at 07:45:43PM +0200, Greg Kurz wrote:
> On Fri, 30 Aug 2019 17:34:13 +0100
> Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> > On Fri, Aug 30, 2019 at 06:13:45PM +0200, Laurent Vivier wrote:
> > > When we hotplug a CPU on memory-less/cpu-less node, the linux kernel
> > > crashes.
> > >
> > > This happens because linux kernel needs to know the NUMA topology at
> > > start to be able to initialize the distance lookup table.
> > >
> > > On pseries, the topology is provided by the firmware via the existing
> > > CPUs and memory information. Thus a node without memory and CPU cannot be
> > > discovered by the kernel.
> > >
> > > To avoid the kernel crash, do not allow to start pseries with empty
> > > nodes.
> >
> > This describes one possible guest OS. Is there any reasonable chance
> > that a non-Linux guest might be able to handle this situation correctly,
> > or do you expect any guest to have the same restriction ?
That's... a more complicated question than you'd think.
The problem here is it's not really obvious in PAPR how topology
information for nodes without memory should be described in the device
tree (which is the only way we given that information to the guest).
It's possible there's some way to encode this information that would
make AIX happy and we just need to fix Linux to cope with that, but
it's not really clear what it would be.
> I can try to grab an AIX image and give a try, but anyway this looks like
> a very big hammer to me... :-\
I'm not really sure why everyone seems to think losing zero-memory
node capability is such a big deal. It's never worked in practice on
POWER and we can always put it back if we figure out a sensible way to
do it.
--
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 --]
next prev parent reply other threads:[~2019-09-02 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 16:13 [Qemu-devel] [PATCH] pseries: do not allow memory-less/cpu-less NUMA node Laurent Vivier
2019-08-30 16:34 ` Daniel P. Berrangé
2019-08-30 17:45 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2019-09-02 6:27 ` David Gibson [this message]
2019-09-02 8:57 ` Daniel P. Berrangé
2019-09-02 9:11 ` David Gibson
2019-09-02 13:58 ` Greg Kurz
2019-09-02 9:14 ` [Qemu-devel] " 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=20190902062718.GG415@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=berrange@redhat.com \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--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 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).