From: Randy Dunlap <rdunlap@infradead.org>
To: paulmck@kernel.org, akpm@linux-foundation.org,
adobriyan@gmail.com, mhiramat@kernel.org
Cc: arnd@kernel.org, ndesaulniers@google.com, sfr@canb.auug.org.au,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH RFC bootconfig 0/2] Distinguish bootloader and embedded kernel parameters
Date: Thu, 27 Jul 2023 21:25:06 -0700 [thread overview]
Message-ID: <cc9ba6e9-1154-ad84-0fef-d67834169110@infradead.org> (raw)
In-Reply-To: <197cba95-3989-4d2f-a9f1-8b192ad08c49@paulmck-laptop>
On 7/27/23 20:35, Paul E. McKenney wrote:
> Hello!
>
> This series provides /proc interfaces parallel to /proc/cmdline that
> provide only those kernel boot parameters that were provided by the
> bootloader (/proc/cmdline_load) and only those parameters that were
> embedded in the kernel image (/proc/cmdline_image, in boot-config format).
> This is especially important when these parameters are presented to the
> boot loader by automation that might gather them from diverse sources,
> and also when a kexec-based reboot process pulls the kernel boot
> parameters from /proc. If such a reboot process uses /proc/cmdline,
> the kernel parameters from the image are replicated on every reboot,
> which can be frustrating when the new kernel has different embedded
> kernel boot parameters.
>
> Why put these in /proc? Because they is quite similar to /proc/cmdline,
> so it makes sense to put it in the same place that /proc/cmdline is
> located.
>
> 1. fs/proc: Add /proc/cmdline_load for boot loader arguments.
>
> 2. fs/proc: Add /proc/cmdline_image for embedded arguments.
>
> Thanx, Paul
>
Hi Paul,
This series seems to be missing updates to
Documentation/filesystems/proc.rst.
Please add them.
Thanks.
> ------------------------------------------------------------------------
>
> b/fs/proc/cmdline.c | 13 +++++++++++++
> b/include/linux/init.h | 3 ++-
> b/init/main.c | 2 +-
> fs/proc/cmdline.c | 12 ++++++++++++
> include/linux/init.h | 11 ++++++-----
> init/main.c | 9 +++++++++
> 6 files changed, 43 insertions(+), 7 deletions(-)
--
~Randy
next prev parent reply other threads:[~2023-07-28 4:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 3:35 [PATCH RFC bootconfig 0/2] Distinguish bootloader and embedded kernel parameters Paul E. McKenney
2023-07-28 3:37 ` [PATCH RFC bootconfig] 1/2] fs/proc: Add /proc/cmdline_load for boot loader arguments Paul E. McKenney
2023-07-28 4:06 ` Stephen Rothwell
2023-07-28 20:52 ` Paul E. McKenney
2023-07-29 14:29 ` Masami Hiramatsu
2023-07-29 16:16 ` Paul E. McKenney
2023-07-30 1:58 ` Masami Hiramatsu
2023-07-30 18:17 ` Paul E. McKenney
2023-08-04 17:23 ` Alexey Dobriyan
2023-08-04 17:36 ` Paul E. McKenney
2023-08-04 18:43 ` Paul E. McKenney
2023-08-07 2:44 ` Masami Hiramatsu
2023-08-07 4:39 ` Paul E. McKenney
2023-08-12 23:30 ` Paul E. McKenney
2023-08-14 23:08 ` Paul E. McKenney
2023-08-16 9:40 ` Masami Hiramatsu
2023-08-16 15:17 ` Masami Hiramatsu
2023-08-16 16:13 ` Paul E. McKenney
2023-08-20 14:14 ` Masami Hiramatsu
2023-08-20 15:40 ` Paul E. McKenney
2023-07-28 3:37 ` [PATCH RFC bootconfig] 2/2] fs/proc: Add /proc/cmdline_image for embedded arguments Paul E. McKenney
2023-07-29 14:23 ` Masami Hiramatsu
2023-07-29 15:41 ` Paul E. McKenney
2023-07-30 1:55 ` Masami Hiramatsu
2023-08-04 17:28 ` Alexey Dobriyan
2023-08-04 17:33 ` Paul E. McKenney
2023-07-28 4:25 ` Randy Dunlap [this message]
2023-07-28 21:05 ` [PATCH RFC bootconfig 0/2] Distinguish bootloader and embedded kernel parameters Paul E. McKenney
2023-07-31 23:30 ` [PATCH RFC v2 bootconfig 0/3] " Paul E. McKenney
2023-07-31 23:31 ` [PATCH RFC v2 bootconfig 1/3] doc: Update /proc/cmdline documentation to include boot config Paul E. McKenney
2023-08-01 1:02 ` Masami Hiramatsu
2023-08-01 2:00 ` Randy Dunlap
2023-08-01 4:00 ` Paul E. McKenney
2023-07-31 23:31 ` [PATCH RFC v2 bootconfig 2/3] fs/proc: Add /proc/cmdline_load for boot loader arguments Paul E. McKenney
2023-07-31 23:31 ` [PATCH RFC v2 bootconfig 3/3] doc: Add /proc/bootconfig to proc.rst Paul E. McKenney
2023-08-01 1:04 ` Masami Hiramatsu
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=cc9ba6e9-1154-ad84-0fef-d67834169110@infradead.org \
--to=rdunlap@infradead.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=ndesaulniers@google.com \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).