From: Breno Leitao <leitao@debian.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, oss@malat.biz, paulmck@kernel.org,
rostedt@goodmis.org, kernel-team@meta.com,
Kiryl Shutsemau <kirill@shutemov.name>
Subject: Re: [PATCH v2] bootconfig: Apply early options from embedded config
Date: Wed, 15 Apr 2026 04:15:57 -0700 [thread overview]
Message-ID: <ad9wwUJ3lh_536Xy@gmail.com> (raw)
In-Reply-To: <adTX6h4Ej5jOcONP@gmail.com>
On Tue, Apr 07, 2026 at 03:19:09AM -0700, Breno Leitao wrote:
> On Fri, Apr 03, 2026 at 11:45:19AM +0900, Masami Hiramatsu wrote:
> > > I'm still uncertain about this approach. The goal is to identify and
> > > categorize the early parameters that are parsed prior to bootconfig
> > > initialization.
> >
> > Yes, if we support early parameters in bootconfig, we need to clarify
> > which parameters are inherently unsupportable, and document it.
> > Currently it is easy to say that it does not support the parameter
> > defined with "early_param()". Similary, maybe we should introduce
> > "arch_param()" or something like it (or support all of them).
> >
> > >
> > > Moreover, this work could become obsolete if bootconfig's initialization
> > > point shifts earlier or later in the boot sequence, necessitating
> > > another comprehensive analysis.
> >
> > If we can init it before calling setup_arch(), yes, we don't need to
> > check it. So that is another option. Do you think it is feasible to
> > support all of them? (Of course, theologically we can do, but the
> > question is the use case and requirements.)
>
> I don't believe all early parameters can be supported by bootconfig.
> Some are inherently incompatible as far as I understand, while others
> depend on bootconfig's initialization point in the boot sequence.
I've developed a patch series that relocates bootconfig initialization
to occur before setup_arch().
Adopting this approach would streamline the categorization considerably,
as only a small subset of kernel parameters are parsed before
setup_arch() is called.
This enables a clearer distinction: parameters processed *before*
setup_arch() versus those handled afterward, rather than classifying
based on what occurs before bootconfig initialization.
Just to close the look and link both discussion together, the proposed
patch series is available at:
https://lore.kernel.org/all/20260415-bootconfig_earlier-v1-0-cf160175de5e@debian.org/
next prev parent reply other threads:[~2026-04-15 11:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 10:05 [PATCH v2] bootconfig: Apply early options from embedded config Breno Leitao
2026-03-25 14:22 ` Masami Hiramatsu
2026-03-26 14:30 ` Masami Hiramatsu
2026-03-27 10:18 ` Breno Leitao
2026-03-27 14:16 ` Masami Hiramatsu
2026-03-27 16:11 ` Breno Leitao
2026-03-27 10:06 ` Breno Leitao
2026-03-27 13:37 ` Masami Hiramatsu
2026-03-30 13:15 ` Breno Leitao
2026-03-30 15:04 ` Breno Leitao
2026-03-31 3:58 ` Masami Hiramatsu
2026-03-31 15:27 ` Breno Leitao
2026-04-01 13:48 ` Masami Hiramatsu
2026-04-01 15:01 ` Breno Leitao
2026-04-03 2:45 ` Masami Hiramatsu
2026-04-07 10:19 ` Breno Leitao
2026-04-15 11:15 ` Breno Leitao [this message]
2026-03-31 0:00 ` Masami Hiramatsu
2026-03-31 10:18 ` Kiryl Shutsemau
2026-04-01 1:02 ` Masami Hiramatsu
2026-04-01 9:40 ` Kiryl Shutsemau
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=ad9wwUJ3lh_536Xy@gmail.com \
--to=leitao@debian.org \
--cc=corbet@lwn.net \
--cc=kernel-team@meta.com \
--cc=kirill@shutemov.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oss@malat.biz \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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