From: Breno Leitao <leitao@debian.org>
To: Masami Hiramatsu <mhiramat@kernel.org>, oss@malat.biz
Cc: catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com,
paulmck@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: arm64: pseudo NMI bootconfig question
Date: Thu, 19 Mar 2026 08:20:27 -0700 [thread overview]
Message-ID: <abwTJBj80oX_T8xt@gmail.com> (raw)
In-Reply-To: <wqzhgeu5vlkeuomajvy7vf3x4gf3fsnzmczmkswvjo7xdyzzbo@6uqjqftbzgot>
hello Masami,
On Thu, Nov 13, 2025 at 02:37:22AM -0800, Breno Leitao wrote:
> On Thu, Nov 13, 2025 at 01:34:03PM +0900, Masami Hiramatsu wrote:
>
> Another possible solution would be to load bootconfig earlier in the
> boot process so that early parameters can be defined within bootconfig.
> Petr suggested this approach some time back, but it doesn't appear to
> have made it upstream.
>
> https://lore.kernel.org/all/20231123194106.08f5832f558fe806b1fd8098@kernel.org/
>
> I'm not fully up to speed on the details of this change, so I want to
> ask directly: Would Petr's approach—allowing early parameters to be set
> via bootconfig make sense from a bootconfig design perspective?
Would it be worthwhile for me to take Petr's patch, update it to the
current codebase, address any issues, and verify that it resolves the
problem described above? If so, would you be open to reviewing and
potentially accepting such a patch?
Thanks,
--breno
next prev parent reply other threads:[~2026-03-19 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 14:05 arm64: pseudo NMI bootconfig question Breno Leitao
2025-11-12 14:21 ` Marc Zyngier
2025-11-13 9:36 ` Breno Leitao
2025-11-13 11:03 ` Will Deacon
2025-11-13 4:34 ` Masami Hiramatsu
2025-11-13 10:37 ` Breno Leitao
2026-03-19 15:20 ` Breno Leitao [this message]
2026-03-20 4:03 ` Masami Hiramatsu
2026-03-24 13:43 ` Breno Leitao
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=abwTJBj80oX_T8xt@gmail.com \
--to=leitao@debian.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@meta.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=oss@malat.biz \
--cc=paulmck@kernel.org \
--cc=will@kernel.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