From: Baoquan He <bhe@redhat.com>
To: mingo@kernel.org, keescook@chromium.org
Cc: linux-kernel@vger.kernel.org, dyoung@redhat.com,
douly.fnst@cn.fujitsu.com, dan.j.williams@intel.com,
hpa@zytor.com, tglx@linutronix.de, x86@kernel.org,
Baoquan He <bhe@redhat.com>
Subject: [PATCH v4 3/3] Documentation/kernel-parameters.txt: Update 'memmap=' option description
Date: Tue, 9 May 2017 13:57:52 +0800 [thread overview]
Message-ID: <1494309472-5691-4-git-send-email-bhe@redhat.com> (raw)
In-Reply-To: <1494309472-5691-1-git-send-email-bhe@redhat.com>
In commit:
9710f581bb4c ("x86, mm: Let "memmap=" take more entries one time")
... 'memmap=' was changed to adopt multiple, comma delimited values in a
single entry, so update the related description.
In the special case of only specifying size value without an offset,
like memmap=nn[KMG], memmap behaves similarly to mem=nn[KMG], so update
it too here.
Furthermore, for memmap=nn[KMG]$ss[KMG], an escape character needs be added
before '$' for some bootloaders. E.g in grub2, if we specify memmap=100M$5G
as suggested by the documentation, "memmap=100MG" gets passed to the kernel.
Clarify all this.
Signed-off-by: Baoquan He <bhe@redhat.com>
---
Documentation/admin-guide/kernel-parameters.txt | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index e4c9e0e..8d37f26 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -2112,6 +2112,12 @@
memmap=nn[KMG]@ss[KMG]
[KNL] Force usage of a specific region of memory.
Region of memory to be used is from ss to ss+nn.
+ If @ss[KMG] is omitted, it equals to mem=nn[KMG]
+ which limits max address as nn[KMG].
+ Multiple different options can be put into one entry
+ with comma delimited to save space:
+ Example:
+ memmap=100M@2G,100M#3G,1G!1024G
memmap=nn[KMG]#ss[KMG]
[KNL,ACPI] Mark specific memory as ACPI data.
@@ -2124,6 +2130,9 @@
memmap=64K$0x18690000
or
memmap=0x10000$0x18690000
+ Some bootloaders may need escape character before '$',
+ like in grub2, otherwise '$' and the following number
+ will be eaten.
memmap=nn[KMG]!ss[KMG]
[KNL,X86] Mark specific memory as protected.
--
2.5.5
prev parent reply other threads:[~2017-05-09 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 5:57 [PATCH v4 0/3] Handle memmap and mem kernel options in boot stage kaslr Baoquan He
2017-05-09 5:57 ` [PATCH v4 1/3] KASLR: Parse all memmap entries in cmdline Baoquan He
2017-05-10 12:29 ` Thomas Gleixner
2017-05-10 13:11 ` Baoquan He
2017-05-09 5:57 ` [PATCH v4 2/3] KASLR: Handle memory limit specified by memmap and mem option Baoquan He
2017-05-09 17:39 ` Kees Cook
2017-05-10 0:35 ` Baoquan He
2017-05-12 4:15 ` Masayoshi Mizuma
2017-05-12 5:06 ` Baoquan He
2017-05-09 5:57 ` Baoquan He [this message]
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=1494309472-5691-4-git-send-email-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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