Re: [PATCHv2 0/7] x86_64/mm: remove bottom-up allocation style by pushing forward the parsing of mem hotplug info

2019-01-14 Thread Pingfan Liu
On Tue, Jan 15, 2019 at 7:02 AM Dave Hansen wrote: > > On 1/10/19 9:12 PM, Pingfan Liu wrote: > > Background > > When kaslr kernel can be guaranteed to sit inside unmovable node > > after [1]. > > What does this "[1]" refer to? > https://lore.kernel.org/patchwork/patch/1029376/ > Also, can you

Re: [PATCHv2 0/7] x86_64/mm: remove bottom-up allocation style by pushing forward the parsing of mem hotplug info

2019-01-14 Thread Dave Hansen
On 1/10/19 9:12 PM, Pingfan Liu wrote: > Background > When kaslr kernel can be guaranteed to sit inside unmovable node > after [1]. What does this "[1]" refer to? Also, can you clarify your terminology here a bit. By "kaslr kernel", do you mean the base address? > But if kaslr kernel is

[PATCHv2 0/7] x86_64/mm: remove bottom-up allocation style by pushing forward the parsing of mem hotplug info

2019-01-10 Thread Pingfan Liu
Background When kaslr kernel can be guaranteed to sit inside unmovable node after [1]. But if kaslr kernel is located near the end of the movable node, then bottom-up allocator may create pagetable which crosses the boundary between unmovable node and movable node. It is a probability issue, two