From: Nikolay Borisov <nik.borisov@suse.com>
To: Borislav Petkov <bp@kernel.org>, X86 ML <x86@kernel.org>
Cc: "Chang S. Bae" <chang.seok.bae@intel.com>,
Sohil Mehta <sohil.mehta@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: Re: [PATCH -v1 2/2] x86/microcode: Add microcode loader debugging functionality
Date: Wed, 20 Aug 2025 18:35:51 +0300 [thread overview]
Message-ID: <6e5503b9-bc5b-4147-836f-8f86f2ac8124@suse.com> (raw)
In-Reply-To: <20250820135043.19048-3-bp@kernel.org>
On 20.08.25 г. 16:50 ч., Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
>
> Instead of adding ad-hoc debugging glue to the microcode loader each
> time I need it, add debugging functionality which is not built by
> default and when built-in, off by default so that it can only be enabled
> explicitly on the command line.
>
> Simulate all patch handling the loader does except the actual loading of
> the microcode patch into the hw.
>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> ---
> .../admin-guide/kernel-parameters.txt | 6 ++
> arch/x86/Kconfig | 12 +++
> arch/x86/kernel/cpu/microcode/amd.c | 88 ++++++++++++++-----
> arch/x86/kernel/cpu/microcode/core.c | 25 +++++-
> arch/x86/kernel/cpu/microcode/internal.h | 10 +++
> 5 files changed, 118 insertions(+), 23 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 9e3bbce6583f..e7badf2aba63 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -3770,6 +3770,12 @@
> microcode= [X86] Control the behavior of the microcode loader.
> Available options, comma separated:
>
> + base_rev=X - with <X> with format: <u32>
> + Set the base microcode revision of each thread when in
> + debug mode.
> +
> + dbg: enable debugging mode when run in a guest
nit: s/in a guest// since nothing in the debug code is really dependent
on whether it's run as a guest or not.
> +
> dis_ucode_ldr: disable the microcode loader
>
> force_minrev:
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index aa250d90f927..77f72f075d89 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1360,6 +1360,18 @@ config MICROCODE_LATE_FORCE_MINREV
>
> If unsure say Y.
>
> +config MICROCODE_DBG
> + bool "Enable microcode loader debugging"
> + default n
> + depends on MICROCODE
> + help
> + Enable code which allows for debugging the microcode loader in
> + a guest. Meaning the patch loading is simulated but everything else
dito, AFAICS it's perfectly fine to have the debug output if not run in
a guest, no ?
> + related to patch parsing and handling is done as on baremetal with
> + the purpose of debugging solely the software side of things.
> +
> + You almost certainly want to say n here.
> +
> config X86_MSR
> tristate "/dev/cpu/*/msr - Model-specific register support"
> help
<snip>
next prev parent reply other threads:[~2025-08-20 15:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 13:50 [PATCH -v1 0/2] x86/microcode: Add debugging glue Borislav Petkov
2025-08-20 13:50 ` [PATCH -v1 1/2] x86/microcode: Add microcode= cmdline parsing Borislav Petkov
2025-08-21 5:03 ` Sohil Mehta
2025-08-21 5:15 ` Chang S. Bae
2025-09-02 8:45 ` kernel test robot
2025-09-04 11:37 ` Borislav Petkov
2025-09-04 23:29 ` Nathan Chancellor
2025-09-05 10:40 ` Borislav Petkov
2025-09-05 13:17 ` Ryusuke Konishi
2025-09-05 19:27 ` Nathan Chancellor
2025-09-05 10:30 ` [tip: x86/microcode] " tip-bot2 for Borislav Petkov (AMD)
2025-08-20 13:50 ` [PATCH -v1 2/2] x86/microcode: Add microcode loader debugging functionality Borislav Petkov
2025-08-20 15:35 ` Nikolay Borisov [this message]
2025-08-20 15:56 ` Borislav Petkov
2025-08-21 5:19 ` Sohil Mehta
2025-08-29 9:45 ` Borislav Petkov
2025-08-29 23:25 ` Sohil Mehta
2025-08-30 9:25 ` Borislav Petkov
2025-09-05 10:30 ` [tip: x86/microcode] " 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=6e5503b9-bc5b-4147-836f-8f86f2ac8124@suse.com \
--to=nik.borisov@suse.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=chang.seok.bae@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sohil.mehta@intel.com \
--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®