From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: <linux-kernel@vger.kernel.org>, <x86@kernel.org>, <hpa@zytor.com>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bhe@redhat.com>,
<keescook@chromium.org>, <yasu.isimatu@gmail.com>
Cc: <indou.takao@jp.fujitsu.com>, <lcapitulino@redhat.com>,
Chao Fan <fanc.fnst@cn.fujitsu.com>
Subject: [PATCH v8 5/5] document: add document for kaslr_mem
Date: Fri, 19 Jan 2018 11:36:47 +0800 [thread overview]
Message-ID: <20180119033647.22469-1-fanc.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <20180117105351.12226-6-fanc.fnst@cn.fujitsu.com>
Signed-off-by: Chao Fan <fanc.fnst@cn.fujitsu.com>
---
Documentation/admin-guide/kernel-parameters.txt | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index e2de7c006a74..28a879f62560 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -2350,6 +2350,16 @@
allocations which rules out almost all kernel
allocations. Use with caution!
+ kaslr_mem=nn[KMG][@ss[KMG]]
+ [KNL] Force usage of a specific region of memory
+ for KASLR during kernel decompression stage.
+ Region of usable memory is from ss to ss+nn. If ss
+ is omitted, it is qeuivalent to kaslr_mem=nn[KMG]@0.
+ Multiple regions can be specified, comma delimited.
+ Notice: we support 4 regions at most now.
+ Example:
+ kaslr_mem=1G,500M@2G,1G@4G
+
MTD_Partition= [MTD]
Format: <name>,<region-number>,<size>,<offset>
--
2.14.3
next prev parent reply other threads:[~2018-01-19 3:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 10:53 [PATCH v7 0/5] x86/KASLR: Add parameter kaslr_mem=nn[KMG]@ss[KMG] Chao Fan
2018-01-17 10:53 ` [PATCH v7 1/5] x86/KASLR: Add kaslr_mem=nn[KMG]@ss[KMG] Chao Fan
2018-01-19 2:34 ` Baoquan He
2018-01-17 10:53 ` [PATCH v7 2/5] x86/KASLR: Handle the memory regions specified in kaslr_mem Chao Fan
2018-01-19 2:39 ` Baoquan He
2018-01-17 10:53 ` [PATCH v7 3/5] x86/KASLR: Give a warning if movable_node specified without kaslr_mem= Chao Fan
2018-01-17 14:02 ` Baoquan He
2018-01-18 1:20 ` Chao Fan
2018-01-17 14:04 ` Baoquan He
2018-01-19 3:31 ` [PATCH v8 " Chao Fan
2018-01-19 3:48 ` Baoquan He
2018-01-17 10:53 ` [PATCH v7 4/5] x86/KASLR: Skip memory mirror handling if movable_node specified Chao Fan
2018-01-17 14:03 ` Baoquan He
2018-01-18 1:13 ` Chao Fan
2018-01-19 3:33 ` [PATCH v8 " Chao Fan
2018-01-19 3:47 ` Baoquan He
2018-01-17 10:53 ` [PATCH v7 5/5] document: add document for kaslr_mem Chao Fan
2018-01-19 3:00 ` Baoquan He
2018-01-19 3:36 ` Chao Fan [this message]
2018-01-19 3:53 ` [PATCH v8 " Baoquan He
2018-01-19 5:27 ` Chao Fan
2018-01-19 5:23 ` [RESEND PATCH " Chao Fan
2018-01-19 18:20 ` Randy Dunlap
2018-01-17 17:32 ` [PATCH v7 0/5] x86/KASLR: Add parameter kaslr_mem=nn[KMG]@ss[KMG] Luiz Capitulino
2018-01-18 1:11 ` Chao Fan
2018-01-18 13:39 ` Luiz Capitulino
2018-01-23 8:35 [PATCH v8 " Chao Fan
2018-01-23 8:35 ` [PATCH v8 5/5] document: add document for kaslr_mem Chao Fan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180119033647.22469-1-fanc.fnst@cn.fujitsu.com \
--to=fanc.fnst@cn.fujitsu.com \
--cc=bhe@redhat.com \
--cc=hpa@zytor.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=keescook@chromium.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yasu.isimatu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).