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
> > > > >
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
> > > > >
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
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;
> -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 ;
> -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;
>
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)
> > > > >
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;
> > > >
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
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
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
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
* 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 @@
> >
* 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
> >
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
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
* 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
* 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
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
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
20 matches
Mail list logo