[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <197cba95-3989-4d2f-a9f1-8b192ad08c49@paulmck-laptop>
Date: Thu, 27 Jul 2023 20:35:10 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: akpm@...ux-foundation.org, adobriyan@...il.com, mhiramat@...nel.org
Cc: arnd@...nel.org, ndesaulniers@...gle.com, paulmck@...nel.org,
sfr@...b.auug.org.au, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-team@...a.com
Subject: [PATCH RFC bootconfig 0/2] Distinguish bootloader and embedded
kernel parameters
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
------------------------------------------------------------------------
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(-)
Powered by blists - more mailing lists