Re: [RFC PATCH 2/4] x86/setup: parse acpi to get hotplug info before init_mem_mapping()

2019-01-07 Thread Pingfan Liu
On Tue, Jan 8, 2019 at 1:11 AM Dave Hansen wrote: > > > On 1/7/19 12:24 AM, Pingfan Liu wrote: > > At present, memblock bottom-up allocation can help us against stamping over > > movable node in very high probability. > > Is this what you are fixing? Making a "high probability", a certainty? >

Re: [RFC PATCH 2/4] x86/setup: parse acpi to get hotplug info before init_mem_mapping()

2019-01-07 Thread Dave Hansen
On 1/7/19 12:24 AM, Pingfan Liu wrote: > At present, memblock bottom-up allocation can help us against stamping over > movable node in very high probability. Is this what you are fixing? Making a "high probability", a certainty? Is this the problem? > diff --git a/arch/x86/kernel/setup.c

Re: [RFC PATCH 2/4] x86/setup: parse acpi to get hotplug info before init_mem_mapping()

2019-01-07 Thread Pingfan Liu
On Mon, Jan 7, 2019 at 4:25 PM Pingfan Liu wrote: > > At present, memblock bottom-up allocation can help us against stamping over > movable node in very high probability. But if the hotplug info has already > been parsed, the memblock allocator can step around the movable node by > itself. This

[RFC PATCH 2/4] x86/setup: parse acpi to get hotplug info before init_mem_mapping()

2019-01-07 Thread Pingfan Liu
At present, memblock bottom-up allocation can help us against stamping over movable node in very high probability. But if the hotplug info has already been parsed, the memblock allocator can step around the movable node by itself. This patch pushes the parsing step forward, just ahead of where,