Re: [PATCH v4 1/3] KASLR: Parse all memmap entries in cmdline

2017-05-10 Thread Baoquan He
On 05/10/17 at 02:29pm, Thomas Gleixner wrote: > On Tue, 9 May 2017, Baoquan He wrote: > > > In commit: > > > > f28442497b5c ("x86/boot: Fix KASLR and memmap= collision") > > > > ... the memmap= option is parsed so that KASLR can avoid those reserved > > regions. It uses cmdline_find_option()

Re: [PATCH v4 1/3] KASLR: Parse all memmap entries in cmdline

2017-05-10 Thread Thomas Gleixner
On Tue, 9 May 2017, Baoquan He wrote: > In commit: > > f28442497b5c ("x86/boot: Fix KASLR and memmap= collision") > > ... the memmap= option is parsed so that KASLR can avoid those reserved > regions. It uses cmdline_find_option() to get the value if memmap= > is specified, however the problem

[PATCH v4 1/3] KASLR: Parse all memmap entries in cmdline

2017-05-08 Thread Baoquan He
In commit: f28442497b5c ("x86/boot: Fix KASLR and memmap= collision") ... the memmap= option is parsed so that KASLR can avoid those reserved regions. It uses cmdline_find_option() to get the value if memmap= is specified, however the problem is that cmdline_find_option() can only find the last