From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>,
linux-tip-commits@vger.kernel.org,
Julian Stecklina <julian.stecklina@cyberus-technology.de>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [tip: x86/boot] x86/boot: Move kernel cmdline setup earlier in the boot process (again)
Date: Mon, 8 Apr 2024 20:27:49 +0200 [thread overview]
Message-ID: <ZhQ3JSXT05Kv/RpM@gmail.com> (raw)
In-Reply-To: <20240408181732.GCZhQ0vGSfP3Gf8tDW@fat_crate.local>
* Borislav Petkov <bp@alien8.de> wrote:
> On Fri, Mar 29, 2024 at 07:51:13AM -0000, tip-bot2 for Julian Stecklina wrote:
> > The following commit has been merged into the x86/boot branch of tip:
> >
> > Commit-ID: 4faa0e5d6d79fc4c6e1943e8b62a65744d8439a0
> > Gitweb: https://git.kernel.org/tip/4faa0e5d6d79fc4c6e1943e8b62a65744d8439a0
> > Author: Julian Stecklina <julian.stecklina@cyberus-technology.de>
> > AuthorDate: Thu, 28 Mar 2024 16:42:12 +01:00
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitterDate: Fri, 29 Mar 2024 08:19:12 +01:00
> >
> > x86/boot: Move kernel cmdline setup earlier in the boot process (again)
>
> ...
>
> > The order is now:
> >
> > setup_arch():
> > -> Assemble final command line:
> > boot_command_line = builtin_cmdline + boot_cmdline
> >
> > -> early_cpu_init()
> > -> early_identify_cpu()
> > -> sld_setup()
> > -> sld_state_setup()
> > -> Looks for split_lock_detect in boot_command_line
> >
> > -> e820__memory_setup()
> >
> > -> parse_early_param()
>
> So that thing. Should we do something like the silly thing below so that
> it catches potential issues with parsing builtin cmdline stuff too early?
Yep, that's a good idea.
Acked-by: Ingo Molnar <mingo@kernel.org>
Ingo
next prev parent reply other threads:[~2024-04-08 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 7:51 [tip: x86/boot] x86/boot: Move kernel cmdline setup earlier in the boot process (again) tip-bot2 for Julian Stecklina
2024-04-08 18:17 ` Borislav Petkov
2024-04-08 18:27 ` Ingo Molnar [this message]
2024-04-09 15:25 ` [PATCH] x86/setup: Warn when option parsing is done too early Borislav Petkov
2024-05-27 17:32 ` [tip: x86/boot] " tip-bot2 for Borislav Petkov (AMD)
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=ZhQ3JSXT05Kv/RpM@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=julian.stecklina@cyberus-technology.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=x86@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