Re: [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

2018-09-11 Thread Baoquan He
On 09/10/18 at 08:18am, Ingo Molnar wrote: > > * Baoquan He wrote: > > > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the > > initial size of the direct mapping region. This is right in the > > old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS, > > 46bit, and

Re: [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

2018-09-11 Thread Baoquan He
On 09/10/18 at 08:18am, Ingo Molnar wrote: > > * Baoquan He wrote: > > > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the > > initial size of the direct mapping region. This is right in the > > old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS, > > 46bit, and

Re: [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

2018-09-10 Thread Ingo Molnar
* Baoquan He wrote: > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the > initial size of the direct mapping region. This is right in the > old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS, > 46bit, and only 4-level mode was supported. > > Later, in commit: >

Re: [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

2018-09-10 Thread Ingo Molnar
* Baoquan He wrote: > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the > initial size of the direct mapping region. This is right in the > old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS, > 46bit, and only 4-level mode was supported. > > Later, in commit: >

[PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

2018-09-09 Thread Baoquan He
In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the initial size of the direct mapping region. This is right in the old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS, 46bit, and only 4-level mode was supported. Later, in commit: b83ce5ee91471d ("x86/mm/64: Make

[PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

2018-09-09 Thread Baoquan He
In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the initial size of the direct mapping region. This is right in the old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS, 46bit, and only 4-level mode was supported. Later, in commit: b83ce5ee91471d ("x86/mm/64: Make