From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Petr Malat <oss@malat.biz>
Cc: paulmck@kernel.org, Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [PATCH 2/2] bootconfig: Apply early options from embedded config
Date: Thu, 23 Nov 2023 23:18:05 +0900 [thread overview]
Message-ID: <20231123231805.b4cb1b96426c956bd35bf53d@kernel.org> (raw)
In-Reply-To: <ZV8jkGVup4KvKiYb@ntb.petris.klfree.czf>
On Thu, 23 Nov 2023 11:04:00 +0100
Petr Malat <oss@malat.biz> wrote:
> Hi!
>
> On Thu, Nov 23, 2023 at 11:22:07AM +0900, Masami Hiramatsu wrote:
> > BTW, we also need to make a block-list for some early params. some of those
> > MUST be passed from the bootloader. E.g. initrd address and size will be
> > passed from the bootloader via commandline. Thus such params in the embedded
> > bootconfig should be filtered at the build time.
>
> It's ok to configure these in the embedded bootconfig - in a case they are
> provided by the bootloader, the bootconfig value is overridden, if not, the
> value from bootconfig is used, so it works as expected.
I meant some params only bootloader knows, like where the initrd is loaded.
Anyway, if user sets such value, it will break the kernel boot as expected :P.
Thank you,
> Petr
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-11-23 14:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 23:13 [PATCH 0/2] bootconfig: Support early options in embedded config Petr Malat
2023-11-21 23:13 ` [PATCH 1/2] bootconfig: Support appending initrd config to embedded one Petr Malat
2023-11-23 2:30 ` Masami Hiramatsu
2023-11-21 23:13 ` [PATCH 2/2] bootconfig: Apply early options from embedded config Petr Malat
2023-11-22 22:47 ` Randy Dunlap
2023-11-22 23:38 ` Paul E. McKenney
2023-11-23 2:22 ` Masami Hiramatsu
2023-11-23 10:04 ` Petr Malat
2023-11-23 14:18 ` Masami Hiramatsu [this message]
2023-11-24 2:12 ` Petr Malat
2023-11-23 17:40 ` Paul E. McKenney
2023-11-23 9:50 ` Petr Malat
2023-11-23 10:41 ` Masami Hiramatsu
2023-11-24 1:58 ` Petr Malat
2023-11-26 22:46 ` Masami Hiramatsu
2023-11-27 15:02 ` Petr Malat
2023-11-27 22:13 ` Masami Hiramatsu
2023-12-05 10:25 ` Petr Malat
2023-11-22 23:34 ` [PATCH 0/2] bootconfig: Support early options in " Paul E. McKenney
2023-11-23 1:58 ` Masami Hiramatsu
2025-07-08 21:00 ` Paul E. McKenney
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=20231123231805.b4cb1b96426c956bd35bf53d@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oss@malat.biz \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.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