Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2018-05-30 Thread Baoquan He
On 05/24/18 at 01:50pm, Mike Travis wrote: > Hi Baoquan, > > My apologies for my delay, we are going through a network reconfig so mail > to me was not available for a bit. Comments below... Not at all. > > > > > > > Is there any chance we can get the size of MMIOH region before mm > > > > >

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2018-05-30 Thread Baoquan He
On 05/24/18 at 01:50pm, Mike Travis wrote: > Hi Baoquan, > > My apologies for my delay, we are going through a network reconfig so mail > to me was not available for a bit. Comments below... Not at all. > > > > > > > Is there any chance we can get the size of MMIOH region before mm > > > > >

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2018-05-17 Thread Mike Travis
On 5/17/2018 8:06 AM, Ramsay, Frank wrote: -Original Message- From: Baoquan He [mailto:b...@redhat.com] Sent: Wednesday, May 16, 2018 11:18 PM To: Travis, Mike ; Anderson, Russ ; Ramsay, Frank Cc: Ingo Molnar

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2018-05-17 Thread Mike Travis
On 5/17/2018 8:06 AM, Ramsay, Frank wrote: -Original Message- From: Baoquan He [mailto:b...@redhat.com] Sent: Wednesday, May 16, 2018 11:18 PM To: Travis, Mike ; Anderson, Russ ; Ramsay, Frank Cc: Ingo Molnar ; linux-kernel@vger.kernel.org; x...@kernel.org; mi...@redhat.com;

RE: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2018-05-17 Thread Ramsay, Frank
> -Original Message- > From: Baoquan He [mailto:b...@redhat.com] > Sent: Wednesday, May 16, 2018 11:18 PM > To: Travis, Mike ; Anderson, Russ > ; Ramsay, Frank > Cc: Ingo Molnar ;

RE: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2018-05-17 Thread Ramsay, Frank
> -Original Message- > From: Baoquan He [mailto:b...@redhat.com] > Sent: Wednesday, May 16, 2018 11:18 PM > To: Travis, Mike ; Anderson, Russ > ; Ramsay, Frank > Cc: Ingo Molnar ; linux-kernel@vger.kernel.org; > x...@kernel.org; mi...@redhat.com; t...@linutronix.de; h...@zytor.com; >

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2018-05-16 Thread Baoquan He
Hi Mike, Russ and Frank, On 09/28/17 at 07:10am, Mike Travis wrote: > > > On 9/28/2017 2:01 AM, Ingo Molnar wrote: > > > > * Baoquan He wrote: > > > > > > > @@ -123,7 +124,7 @@ void __init kernel_randomize_memory(void) > > > > >

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2018-05-16 Thread Baoquan He
Hi Mike, Russ and Frank, On 09/28/17 at 07:10am, Mike Travis wrote: > > > On 9/28/2017 2:01 AM, Ingo Molnar wrote: > > > > * Baoquan He wrote: > > > > > > > @@ -123,7 +124,7 @@ void __init kernel_randomize_memory(void) > > > > > CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING; > > > >

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-30 Thread Baoquan He
Hi Mike, On 09/28/17 at 07:10am, Mike Travis wrote: > > > On 9/28/2017 2:01 AM, Ingo Molnar wrote: > > > > > If on SGI UV system, the kaslr_regions[0].size_tb, namely the size of > > > the direct mapping section, is incorrect. > > > > > > Its direct mapping size includes two parts: > > > #1

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-30 Thread Baoquan He
Hi Mike, On 09/28/17 at 07:10am, Mike Travis wrote: > > > On 9/28/2017 2:01 AM, Ingo Molnar wrote: > > > > > If on SGI UV system, the kaslr_regions[0].size_tb, namely the size of > > > the direct mapping section, is incorrect. > > > > > > Its direct mapping size includes two parts: > > > #1

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-28 Thread Mike Travis
On 9/28/2017 2:01 AM, Ingo Molnar wrote: * Baoquan He wrote: Hi Ingo, On 09/28/17 at 09:56am, Ingo Molnar wrote: diff --git a/arch/x86/mm/kaslr.c b/arch/x86/mm/kaslr.c index af599167fe3c..4d68c08df82d 100644 --- a/arch/x86/mm/kaslr.c +++ b/arch/x86/mm/kaslr.c @@ -27,6

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-28 Thread Mike Travis
On 9/28/2017 2:01 AM, Ingo Molnar wrote: * Baoquan He wrote: Hi Ingo, On 09/28/17 at 09:56am, Ingo Molnar wrote: diff --git a/arch/x86/mm/kaslr.c b/arch/x86/mm/kaslr.c index af599167fe3c..4d68c08df82d 100644 --- a/arch/x86/mm/kaslr.c +++ b/arch/x86/mm/kaslr.c @@ -27,6 +27,7 @@ #include

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-28 Thread Ingo Molnar
* Baoquan He wrote: > Hi Ingo, > > On 09/28/17 at 09:56am, Ingo Molnar wrote: > > > diff --git a/arch/x86/mm/kaslr.c b/arch/x86/mm/kaslr.c > > > index af599167fe3c..4d68c08df82d 100644 > > > --- a/arch/x86/mm/kaslr.c > > > +++ b/arch/x86/mm/kaslr.c > > > @@ -27,6 +27,7 @@ > >

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-28 Thread Ingo Molnar
* Baoquan He wrote: > Hi Ingo, > > On 09/28/17 at 09:56am, Ingo Molnar wrote: > > > diff --git a/arch/x86/mm/kaslr.c b/arch/x86/mm/kaslr.c > > > index af599167fe3c..4d68c08df82d 100644 > > > --- a/arch/x86/mm/kaslr.c > > > +++ b/arch/x86/mm/kaslr.c > > > @@ -27,6 +27,7 @@ > > > #include > >

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-28 Thread Baoquan He
Hi Ingo, On 09/28/17 at 09:56am, Ingo Molnar wrote: > > diff --git a/arch/x86/mm/kaslr.c b/arch/x86/mm/kaslr.c > > index af599167fe3c..4d68c08df82d 100644 > > --- a/arch/x86/mm/kaslr.c > > +++ b/arch/x86/mm/kaslr.c > > @@ -27,6 +27,7 @@ > > #include > > #include > > #include > > +#include

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-28 Thread Baoquan He
Hi Ingo, On 09/28/17 at 09:56am, Ingo Molnar wrote: > > diff --git a/arch/x86/mm/kaslr.c b/arch/x86/mm/kaslr.c > > index af599167fe3c..4d68c08df82d 100644 > > --- a/arch/x86/mm/kaslr.c > > +++ b/arch/x86/mm/kaslr.c > > @@ -27,6 +27,7 @@ > > #include > > #include > > #include > > +#include

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-28 Thread Ingo Molnar
* Baoquan He wrote: > On SGI UV system, kernel often hangs when KASLR is enabled. Disabling > KASLR makes kernel work well. > > The back trace is: > > kernel BUG at arch/x86/mm/init_64.c:311! > invalid opcode: [#1] SMP > [...] > RIP: 0010:__init_extra_mapping+0x188/0x196

Re: [PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-28 Thread Ingo Molnar
* Baoquan He wrote: > On SGI UV system, kernel often hangs when KASLR is enabled. Disabling > KASLR makes kernel work well. > > The back trace is: > > kernel BUG at arch/x86/mm/init_64.c:311! > invalid opcode: [#1] SMP > [...] > RIP: 0010:__init_extra_mapping+0x188/0x196 > [...] > Call

[PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-07 Thread Baoquan He
On SGI UV system, kernel often hangs when KASLR is enabled. Disabling KASLR makes kernel work well. The back trace is: kernel BUG at arch/x86/mm/init_64.c:311! invalid opcode: [#1] SMP [...] RIP: 0010:__init_extra_mapping+0x188/0x196 [...] Call Trace: init_extra_mapping_uc+0x13/0x15

[PATCH v2 RESEND 2/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

2017-09-07 Thread Baoquan He
On SGI UV system, kernel often hangs when KASLR is enabled. Disabling KASLR makes kernel work well. The back trace is: kernel BUG at arch/x86/mm/init_64.c:311! invalid opcode: [#1] SMP [...] RIP: 0010:__init_extra_mapping+0x188/0x196 [...] Call Trace: init_extra_mapping_uc+0x13/0x15