From: Michal Hocko <mhocko@kernel.org>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
jgross@suse.com, william.kucharski@oracle.com, mingo@kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] mm/hotplug: Only respect mem= parameter during boot stage
Date: Tue, 10 Dec 2019 14:32:02 +0100 [thread overview]
Message-ID: <20191210133202.GJ10404@dhcp22.suse.cz> (raw)
In-Reply-To: <20191210125557.GA28917@MiWiFi-R3L-srv>
On Tue 10-12-19 20:55:57, Baoquan He wrote:
[...]
> Btw, as you said at above, I am confused by the '[KNL,BOOT]', what does
> the 'BOOT' mean in the documentation of 'mem='? I checked all parameters
> with 'BOOT', still don't get it clearly.
This is a good question indeed. I have checked closer and this is what
documentation says
Documentation/admin-guide/kernel-parameters.rst
"
BOOT Is a boot loader parameter.
Parameters denoted with BOOT are actually interpreted by the boot
loader, and have no meaning to the kernel directly.
"
and that really doesn't fit, right? So I went to check the full history
git tree just to get to 2.4.0-test5 and no explanation whatsoever.
Fun, isn't it? ;)
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-12-10 13:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 15:05 Baoquan He
2019-12-09 9:43 ` David Hildenbrand
2019-12-09 10:07 ` Michal Hocko
2019-12-09 10:24 ` Jürgen Groß
2019-12-09 11:01 ` David Hildenbrand
2019-12-09 11:08 ` Jürgen Groß
2019-12-09 11:11 ` David Hildenbrand
2019-12-10 8:04 ` Baoquan He
2019-12-10 7:24 ` Baoquan He
2019-12-10 10:28 ` Michal Hocko
2019-12-10 10:43 ` Baoquan He
2019-12-10 11:33 ` Michal Hocko
2019-12-10 12:55 ` Baoquan He
2019-12-10 13:32 ` Michal Hocko [this message]
2019-12-10 14:05 ` Baoquan He
2019-12-10 14:19 ` Michal Hocko
2019-12-11 13:20 ` Baoquan He
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=20191210133202.GJ10404@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=william.kucharski@oracle.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
all inboxes | Powered by JetHome®