Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-23 Thread Baoquan He
On 04/18/17 at 02:51pm, Ingo Molnar wrote: > > * Baoquan He wrote: > > > On 04/18/17 at 11:47am, Ingo Molnar wrote: > > > I ported this series to tip:x86/boot (please post future versions against > > > that), > > > and beyond a trivial conflict with e820entry => e820_entry,

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-23 Thread Baoquan He
On 04/18/17 at 02:51pm, Ingo Molnar wrote: > > * Baoquan He wrote: > > > On 04/18/17 at 11:47am, Ingo Molnar wrote: > > > I ported this series to tip:x86/boot (please post future versions against > > > that), > > > and beyond a trivial conflict with e820entry => e820_entry, it fails to > > >

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-20 Thread Baoquan He
On 04/18/17 at 02:51pm, Ingo Molnar wrote: > > * Baoquan He wrote: > > > On 04/18/17 at 11:47am, Ingo Molnar wrote: > > > > > > * Baoquan He wrote: > > > > > > > People reported kernel panic occurs during system boots up with mem > > > > boot option. > > >

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-20 Thread Baoquan He
On 04/18/17 at 02:51pm, Ingo Molnar wrote: > > * Baoquan He wrote: > > > On 04/18/17 at 11:47am, Ingo Molnar wrote: > > > > > > * Baoquan He wrote: > > > > > > > People reported kernel panic occurs during system boots up with mem > > > > boot option. > > > > After checking code, several

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-18 Thread Baoquan He
On 04/18/17 at 02:51pm, Ingo Molnar wrote: > > > I ported this series to tip:x86/boot (please post future versions against > > > that), > > > and beyond a trivial conflict with e820entry => e820_entry, it fails to > > > build on > > > 32-bit allmodconfig: > > > > > > ld: -r and -shared may

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-18 Thread Baoquan He
On 04/18/17 at 02:51pm, Ingo Molnar wrote: > > > I ported this series to tip:x86/boot (please post future versions against > > > that), > > > and beyond a trivial conflict with e820entry => e820_entry, it fails to > > > build on > > > 32-bit allmodconfig: > > > > > > ld: -r and -shared may

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-18 Thread Ingo Molnar
* Baoquan He wrote: > On 04/18/17 at 11:47am, Ingo Molnar wrote: > > > > * Baoquan He wrote: > > > > > People reported kernel panic occurs during system boots up with mem boot > > > option. > > > After checking code, several problems are found about memmap=

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-18 Thread Ingo Molnar
* Baoquan He wrote: > On 04/18/17 at 11:47am, Ingo Molnar wrote: > > > > * Baoquan He wrote: > > > > > People reported kernel panic occurs during system boots up with mem boot > > > option. > > > After checking code, several problems are found about memmap= and mem= in > > > boot stage > >

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-18 Thread Baoquan He
On 04/18/17 at 11:47am, Ingo Molnar wrote: > > * Baoquan He wrote: > > > People reported kernel panic occurs during system boots up with mem boot > > option. > > After checking code, several problems are found about memmap= and mem= in > > boot stage > > kaslr. > > > > *) In

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-18 Thread Baoquan He
On 04/18/17 at 11:47am, Ingo Molnar wrote: > > * Baoquan He wrote: > > > People reported kernel panic occurs during system boots up with mem boot > > option. > > After checking code, several problems are found about memmap= and mem= in > > boot stage > > kaslr. > > > > *) In commit

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-18 Thread Ingo Molnar
* Baoquan He wrote: > People reported kernel panic occurs during system boots up with mem boot > option. > After checking code, several problems are found about memmap= and mem= in > boot stage > kaslr. > > *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap=

Re: [PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-18 Thread Ingo Molnar
* Baoquan He wrote: > People reported kernel panic occurs during system boots up with mem boot > option. > After checking code, several problems are found about memmap= and mem= in > boot stage > kaslr. > > *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only > one

[PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-17 Thread Baoquan He
People reported kernel panic occurs during system boots up with mem boot option. After checking code, several problems are found about memmap= and mem= in boot stage kaslr. *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only one memmap entry is considered and only

[PATCH 0/4] Handle memmap and mem kernel options in boot stage kaslr

2017-04-17 Thread Baoquan He
People reported kernel panic occurs during system boots up with mem boot option. After checking code, several problems are found about memmap= and mem= in boot stage kaslr. *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only one memmap entry is considered and only