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

2018-09-08 Thread Baoquan He
On 09/08/18 at 02:10pm, Thomas Gleixner wrote: > On Wed, 29 Aug 2018, 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

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

2018-09-08 Thread Baoquan He
On 09/08/18 at 02:10pm, Thomas Gleixner wrote: > On Wed, 29 Aug 2018, 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

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

2018-09-08 Thread Thomas Gleixner
On Wed, 29 Aug 2018, 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. > >

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

2018-09-08 Thread Thomas Gleixner
On Wed, 29 Aug 2018, 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. > >

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

2018-09-04 Thread Thomas Garnier
Thanks Baoquan! Reviewed-by: Thomas Garnier On Wed, Aug 29, 2018 at 4:49 AM Kirill A. Shutemov wrote: > > On Wed, Aug 29, 2018 at 10:17:53AM +0800, Baoquan He wrote: > > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the > > initial size of the direct mapping region. This is

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

2018-09-04 Thread Thomas Garnier
Thanks Baoquan! Reviewed-by: Thomas Garnier On Wed, Aug 29, 2018 at 4:49 AM Kirill A. Shutemov wrote: > > On Wed, Aug 29, 2018 at 10:17:53AM +0800, Baoquan He wrote: > > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the > > initial size of the direct mapping region. This is

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

2018-08-29 Thread Kirill A. Shutemov
On Wed, Aug 29, 2018 at 10:17:53AM +0800, 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

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

2018-08-29 Thread Kirill A. Shutemov
On Wed, Aug 29, 2018 at 10:17:53AM +0800, 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

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

2018-08-28 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 1/2] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

2018-08-28 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