On Wed, Sep 04, 2019 at 02:22:39PM +0800, Tao Xu wrote:
> On 9/4/2019 1:52 AM, Eduardo Habkost wrote:
> > On Mon, Aug 05, 2019 at 03:13:02PM +0800, Tao Xu wrote:
> > > Add MachineClass::auto_enable_numa field. When it is true, a NUMA node
> > > is expected to be created implicitly.
> > >
> > > Acked-by: David Gibson <da...@gibson.dropbear.id.au>
> > > Suggested-by: Igor Mammedov <imamm...@redhat.com>
> > > Suggested-by: Eduardo Habkost <ehabk...@redhat.com>
> > > Signed-off-by: Tao Xu <tao3...@intel.com>
> >
> > This introduces spurious warnings when running qemu-system-ppc64.
> > See:
> > https://lore.kernel.org/qemu-devel/CAFEAcA-AvFS2cbDH-t5SxgY9hA=lgl81_8dn-vh193vtv9w...@mail.gmail.com/
> >
> > To reproduce it, just run 'qemu-system-ppc64 -machine pseries'
> > without any -numa arguments.
> >
> > I have removed this patch from machine-next so it won't block the
> > existing pull request.
> >
> I got it. If default splitting of RAM between nodes is
> deprecated, this patch can't reuse the splitting code. I agree with droping
> this patch.
Probably all we need to fix this issue is to replace
NumaNodeOptions node = { };
with
NumaNodeOptions node = { .size = ram_size };
in the auto_enable_numa block.
Do you plan to send v2?
--
Eduardo
