[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5caa647b-22cb-6b77-eb4c-bd0ef1f70b7f@infradead.org>
Date: Mon, 15 Jan 2018 14:40:35 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Chao Fan <fanc.fnst@...fujitsu.com>, linux-kernel@...r.kernel.org,
x86@...nel.org, hpa@...or.com, tglx@...utronix.de,
mingo@...hat.com, bhe@...hat.com, keescook@...omium.org,
yasu.isimatu@...il.com
Cc: indou.takao@...fujitsu.com, lcapitulino@...hat.com
Subject: Re: [PATCH v6 1/5] kaslr: add kaslr_mem=nn[KMG]@ss[KMG] to specify
extracting memory
On 01/15/2018 04:40 AM, Chao Fan wrote:
> In current code, kaslr only has a method to avoid some memory regions,
> but no method to specify the regions for kaslr to extract. So kaslr
> may choose the wrong position sometimes, which will cause some other
> features fail.
>
> Here is a problem that kaslr may choose the memory region in movable
> nodes to extract kernel, which will make the nodes can't be hot-removed.
> To solve it, we can specify the memory region in immovable node.
> Create "kaslr_mem=" to store the regions in immovable nodes, where should
> be chosen by kaslr.
>
> Also change the "handle_mem_memmap" to "handle_mem_filter", since
> it will not only handle memmap parameter now.
Hi,
Are any of the kernel command-line parameters documented anywhere?
Thanks.
> Multiple regions can be specified, comma delimited.
> Considering the usage of memory, only support for 4 regions.
> 4 regions contains 2 nodes at least, enough for kernel to extract.
>
> Signed-off-by: Chao Fan <fanc.fnst@...fujitsu.com>
> ---
> arch/x86/boot/compressed/kaslr.c | 73 ++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 70 insertions(+), 3 deletions(-)
--
~Randy
Powered by blists - more mailing lists