From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Borislav Petkov <bp@kernel.org>, X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: Re: [PATCH 1/2] x86/microcode: Add microcode= cmdline parsing
Date: Thu, 14 Aug 2025 16:08:57 -0700 [thread overview]
Message-ID: <6b345bdd-d5f6-4967-9f2a-15c2d371ef1b@intel.com> (raw)
In-Reply-To: <20250809094206.28028-2-bp@kernel.org>
On 8/9/2025 2:42 AM, Borislav Petkov wrote:
>
> - microcode.force_minrev= [X86]
> - Format: <bool>
> + microcode= [X86] Control the behavior of the microcode loader.
> + Available options, comma separated:
It looks like microcode=dis_ucode_ldr is also supported.
This could be added here:
ldr_ucode_ldr
Disable the microcode loader.
> + force_minrev
> Enable or disable the microcode minimal revision
> - enforcement for the runtime microcode loader.
> + enforcement for the runtime microcode loader.
I also noticed in arch/x86/Kconfig:
config MICROCODE_LATE_LOADING
bool "Late microcode loading (DANGEROUS)"
default n
depends on MICROCODE && SMP
help
...
the kernel command line with "microcode.minrev=Y".
This outdated has been there already. Perhaps, it might be better to fix
this typo with the new one while updating the option.
> -bool force_minrev = IS_ENABLED(CONFIG_MICROCODE_LATE_FORCE_MINREV);
> -module_param(force_minrev, bool, S_IRUSR | S_IWUSR);
> +bool force_minrev = false;
<snip>
> +static void early_parse_cmdline(void)
> +{
> + char cmd_buf[64] = {};
> + char *s, *p = cmd_buf;
> +
> + if (cmdline_find_option(boot_command_line, "microcode", cmd_buf, 64) > 0) {
nit: s/64/sizeof(cmd_bug)/
> + while ((s = strsep(&p, ","))) {
> + if (IS_ENABLED(CONFIG_MICROCODE_LATE_FORCE_MINREV)) {
> + if (!strcmp("force_minrev", s))
> + force_minrev = true;
> + }
I think the behavior here differs from before:
Previously, the minrev requirement could be enforced by either
(a) Build with MICROCODE_LATE_FORCE_MINREV=y, or
(b) microcode.force_minrev with MICROCODE_LATE=y.
Now, this requires both. I don't know this is intentional, but it’s like
asking for more from the user.
Thanks,
Chang
next prev parent reply other threads:[~2025-08-14 23:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 9:42 [PATCH 0/2] x86/microcode: Add debugging glue Borislav Petkov
2025-08-09 9:42 ` [PATCH 1/2] x86/microcode: Add microcode= cmdline parsing Borislav Petkov
2025-08-12 2:26 ` Sohil Mehta
2025-08-12 10:23 ` Borislav Petkov
2025-08-12 19:14 ` Sohil Mehta
2025-08-12 21:28 ` Borislav Petkov
2025-08-14 23:08 ` Chang S. Bae [this message]
2025-08-15 9:20 ` Borislav Petkov
2025-08-15 19:50 ` Chang S. Bae
2025-08-18 16:30 ` Sohil Mehta
2025-08-09 9:42 ` [PATCH 2/2] x86/microcode: Add microcode loader debugging functionality Borislav Petkov
2025-08-12 3:04 ` Sohil Mehta
2025-08-12 10:26 ` Borislav Petkov
2025-08-12 18:57 ` Sohil Mehta
2025-08-12 19:09 ` Borislav Petkov
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=6b345bdd-d5f6-4967-9f2a-15c2d371ef1b@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®