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
Subject: Re: [PATCH v2] bootconfig: Apply early options from embedded config
Date: Mon, 30 Mar 2026 06:15:17 -0700 [thread overview]
Message-ID: <acpzhCBEPh-tKVqg@gmail.com> (raw)
In-Reply-To: <20260327223744.f246150adc1671f7605a4f0a@kernel.org>
On Fri, Mar 27, 2026 at 10:37:44PM +0900, Masami Hiramatsu wrote:
> On Fri, 27 Mar 2026 03:06:41 -0700
> Breno Leitao <leitao@debian.org> wrote:
> > > To fix this, we need to change setup_arch() for each architecture so
> > > that it calls this bootconfig_apply_early_params().
> >
> > Could we instead integrate this into parse_early_param() itself? That
> > approach would avoid the need to modify each architecture individually.
>
> Ah, indeed.
I investigated integrating bootconfig into parse_early_param() and hit a
blocker: xbc_init() and xbc_make_cmdline() depend on memblock_alloc(), but on
most architectures (x86, arm64, arm, s390, riscv) parse_early_param() is called
from setup_arch() _before_ memblock is initialized.
So, bootconfig will not be available as early as parse_early_param().
An alternative is replace memblock allocations in lib/bootconfig.c with static
__initdata buffers, similar to Petr's approach in 2023:
https://lore.kernel.org/all/20231121231342.193646-3-oss@malat.biz/
But, there was concerns about the allocation size:
Petr Malat <oss@malat.biz> wrote:
> To allow handling of early options, it's necessary to eliminate allocations
> from embedded bootconfig handling
"Hm, my concern is that this can introduce some sort of overhead to parse the bootconfig."
next prev parent reply other threads:[~2026-03-30 13:15 UTC|newest]
Thread overview: 19+ 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 [this message]
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-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=acpzhCBEPh-tKVqg@gmail.com \
--to=leitao@debian.org \
--cc=corbet@lwn.net \
--cc=kernel-team@meta.com \
--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