Re: [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size
From: Baoquan He
Date: Tue Sep 11 2018 - 03:22:18 EST
On 09/10/18 at 08:18am, Ingo Molnar wrote:
> * Baoquan He <bhe@xxxxxxxxxx> 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.
> - what does 'memory KASLR' mean? All KASLR deals with memory.
Thanks for your reviewing. I have updated patch log according to your
comments. For this one, Thomas Garnier calls it memory section KASLR, to
differentiate with kernel text KASLR. I would like to call it memory region
KASLR, is it OK?
Paste the updated patch here.