Re: [PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-03 Thread Thomas Garnier
On Mon, May 2, 2016 at 2:58 PM, Dave Hansen wrote: > On 05/02/2016 02:41 PM, Thomas Garnier wrote: >> Minor change that allows early boot physical mapping of PUD level virtual >> addresses. This change prepares usage of different virtual addresses for >> KASLR memory

Re: [PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-03 Thread Thomas Garnier
On Mon, May 2, 2016 at 2:58 PM, Dave Hansen wrote: > On 05/02/2016 02:41 PM, Thomas Garnier wrote: >> Minor change that allows early boot physical mapping of PUD level virtual >> addresses. This change prepares usage of different virtual addresses for >> KASLR memory randomization. It has no

Re: [PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-03 Thread Dave Hansen
On 05/03/2016 03:05 AM, Baoquan He wrote: > I have a tiny concern about phys_pmd_init(), both phys_pud_init and > phys_pte_init name 2nd parameter as 'addr', phys_pmd_init use 'address'. > If this can be changed to make them look consistent completist would > have a good sleep from now on. Yes,

Re: [PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-03 Thread Dave Hansen
On 05/03/2016 03:05 AM, Baoquan He wrote: > I have a tiny concern about phys_pmd_init(), both phys_pud_init and > phys_pte_init name 2nd parameter as 'addr', phys_pmd_init use 'address'. > If this can be changed to make them look consistent completist would > have a good sleep from now on. Yes,

Re: [PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-03 Thread Baoquan He
On 05/02/16 at 02:58pm, Dave Hansen wrote: > On 05/02/2016 02:41 PM, Thomas Garnier wrote: > > Minor change that allows early boot physical mapping of PUD level virtual > > addresses. This change prepares usage of different virtual addresses for > > KASLR memory randomization. It has no impact on

Re: [PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-03 Thread Baoquan He
On 05/02/16 at 02:58pm, Dave Hansen wrote: > On 05/02/2016 02:41 PM, Thomas Garnier wrote: > > Minor change that allows early boot physical mapping of PUD level virtual > > addresses. This change prepares usage of different virtual addresses for > > KASLR memory randomization. It has no impact on

Re: [PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-02 Thread Dave Hansen
On 05/02/2016 02:41 PM, Thomas Garnier wrote: > Minor change that allows early boot physical mapping of PUD level virtual > addresses. This change prepares usage of different virtual addresses for > KASLR memory randomization. It has no impact on default usage. ... > diff --git

Re: [PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-02 Thread Dave Hansen
On 05/02/2016 02:41 PM, Thomas Garnier wrote: > Minor change that allows early boot physical mapping of PUD level virtual > addresses. This change prepares usage of different virtual addresses for > KASLR memory randomization. It has no impact on default usage. ... > diff --git

[PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-02 Thread Thomas Garnier
Minor change that allows early boot physical mapping of PUD level virtual addresses. This change prepares usage of different virtual addresses for KASLR memory randomization. It has no impact on default usage. Signed-off-by: Thomas Garnier --- Based on next-20160502 ---

[PATCH v2 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

2016-05-02 Thread Thomas Garnier
Minor change that allows early boot physical mapping of PUD level virtual addresses. This change prepares usage of different virtual addresses for KASLR memory randomization. It has no impact on default usage. Signed-off-by: Thomas Garnier --- Based on next-20160502 --- arch/x86/mm/init_64.c |