Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On Mon, 28 May 2018 17:54:18 +0800 Baoquan He wrote: > On 05/23/18 at 03:10pm, Luiz Capitulino wrote: > > On Fri, 18 May 2018 19:28:36 +0800 > > Baoquan He wrote: > > > > > > Note that it's not KASLR specific: if we had some other kernel feature > > > > that tried > > > > to allocate a

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On Mon, 28 May 2018 17:54:18 +0800 Baoquan He wrote: > On 05/23/18 at 03:10pm, Luiz Capitulino wrote: > > On Fri, 18 May 2018 19:28:36 +0800 > > Baoquan He wrote: > > > > > > Note that it's not KASLR specific: if we had some other kernel feature > > > > that tried > > > > to allocate a

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On 05/23/18 at 03:10pm, Luiz Capitulino wrote: > On Fri, 18 May 2018 19:28:36 +0800 > Baoquan He wrote: > > > > Note that it's not KASLR specific: if we had some other kernel feature > > > that tried > > > to allocate a piece of memory from what appears to be perfectly usable

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On 05/23/18 at 03:10pm, Luiz Capitulino wrote: > On Fri, 18 May 2018 19:28:36 +0800 > Baoquan He wrote: > > > > Note that it's not KASLR specific: if we had some other kernel feature > > > that tried > > > to allocate a piece of memory from what appears to be perfectly usable > > > generic

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On Fri, 18 May 2018 19:28:36 +0800 Baoquan He wrote: > > Note that it's not KASLR specific: if we had some other kernel feature that > > tried > > to allocate a piece of memory from what appears to be perfectly usable > > generic RAM > > we'd have the same problems! > >

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On Fri, 18 May 2018 19:28:36 +0800 Baoquan He wrote: > > Note that it's not KASLR specific: if we had some other kernel feature that > > tried > > to allocate a piece of memory from what appears to be perfectly usable > > generic RAM > > we'd have the same problems! > > Hmm, this may not

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On 05/18/18 at 07:28pm, Baoquan He wrote: > On 05/18/18 at 10:19am, Ingo Molnar wrote: > > > > * Baoquan He wrote: > > > > > OK, I realized my saying above is misled because I didn't explain the > > > background clearly. Let me add it: > > > > > > Previously, FJ reported the

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On 05/18/18 at 07:28pm, Baoquan He wrote: > On 05/18/18 at 10:19am, Ingo Molnar wrote: > > > > * Baoquan He wrote: > > > > > OK, I realized my saying above is misled because I didn't explain the > > > background clearly. Let me add it: > > > > > > Previously, FJ reported the movable_node issue

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On 05/18/18 at 10:19am, Ingo Molnar wrote: > > * Baoquan He wrote: > > > OK, I realized my saying above is misled because I didn't explain the > > background clearly. Let me add it: > > > > Previously, FJ reported the movable_node issue that KASLR will put > > kernel into

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On 05/18/18 at 10:19am, Ingo Molnar wrote: > > * Baoquan He wrote: > > > OK, I realized my saying above is misled because I didn't explain the > > background clearly. Let me add it: > > > > Previously, FJ reported the movable_node issue that KASLR will put > > kernel into movable_node. That

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

* Baoquan He wrote: > OK, I realized my saying above is misled because I didn't explain the > background clearly. Let me add it: > > Previously, FJ reported the movable_node issue that KASLR will put > kernel into movable_node. That cause those movable_nodes can't be hot >

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

* Baoquan He wrote: > OK, I realized my saying above is misled because I didn't explain the > background clearly. Let me add it: > > Previously, FJ reported the movable_node issue that KASLR will put > kernel into movable_node. That cause those movable_nodes can't be hot > plugged any more. So

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On 05/18/18 at 09:00am, Ingo Molnar wrote: > > * Baoquan He wrote: > > > This is a regression bug fix. Luiz's team reported that 1GB huge page > > allocation will get one less 1GB page randomly when KASLR is enabled. On > > their KVM guest with 4GB RAM, which only has one good

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

On 05/18/18 at 09:00am, Ingo Molnar wrote: > > * Baoquan He wrote: > > > This is a regression bug fix. Luiz's team reported that 1GB huge page > > allocation will get one less 1GB page randomly when KASLR is enabled. On > > their KVM guest with 4GB RAM, which only has one good 1GB huge page, >

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

* Baoquan He wrote: > This is a regression bug fix. Luiz's team reported that 1GB huge page > allocation will get one less 1GB page randomly when KASLR is enabled. On > their KVM guest with 4GB RAM, which only has one good 1GB huge page, > they found the 1GB huge page

Re: [PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

* Baoquan He wrote: > This is a regression bug fix. Luiz's team reported that 1GB huge page > allocation will get one less 1GB page randomly when KASLR is enabled. On > their KVM guest with 4GB RAM, which only has one good 1GB huge page, > they found the 1GB huge page allocation sometime failed

[PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

This is a regression bug fix. Luiz's team reported that 1GB huge page allocation will get one less 1GB page randomly when KASLR is enabled. On their KVM guest with 4GB RAM, which only has one good 1GB huge page, they found the 1GB huge page allocation sometime failed with below kernel option

[PATCH 0/2] x86/boot/KASLR: Skip specified number of 1GB huge pages when do physical randomization

This is a regression bug fix. Luiz's team reported that 1GB huge page allocation will get one less 1GB page randomly when KASLR is enabled. On their KVM guest with 4GB RAM, which only has one good 1GB huge page, they found the 1GB huge page allocation sometime failed with below kernel option