[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200206234100.953b48ecef04f97c112d2e8b@kernel.org>
Date: Thu, 6 Feb 2020 23:41:00 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [for-next][PATCH 04/26] bootconfig: Add Extra Boot Config
support
Hi,
On Thu, 6 Feb 2020 12:54:05 +0100
Borislav Petkov <bp@...en8.de> wrote:
> On Tue, Jan 14, 2020 at 04:03:20PM -0500, Steven Rostedt wrote:
> > diff --git a/init/Kconfig b/init/Kconfig
> > index a34064a031a5..63450d3bbf12 100644
> > --- a/init/Kconfig
> > +++ b/init/Kconfig
> > @@ -1215,6 +1215,17 @@ source "usr/Kconfig"
> >
> > endif
> >
> > +config BOOT_CONFIG
> > + bool "Boot config support"
> > + select LIBXBC
> > + default y
>
> Any particular reason this is default y? Why should it be enabled by
> default on all boxes?
Oh, you are not the first person asked that :)
https://lkml.org/lkml/2019/12/9/563
And yes, I think this is important that will useful for most developers
and admins. Since the bootconfig already covers kernel and init options,
this can be a new standard way to pass args to kernel boot.
And as I reported above thread, the memory footpoint of view, most code
and working memory are released after boot. Also, as Linus's suggested,
now this feature is enabled only if user gives "bootconfig" on the kernel
command line. So the side effect is minimized.
Thank you,
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists