From: Borislav Petkov <bp@kernel.org>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: [PATCH 0/2] x86/microcode: Add debugging glue
Date: Sat, 9 Aug 2025 11:42:04 +0200 [thread overview]
Message-ID: <20250809094206.28028-1-bp@kernel.org> (raw)
From: "Borislav Petkov (AMD)" <bp@alien8.de>
Hi,
this is something I've been meaning to do for a long time: each time when
doing despicable things to the loader, I get to add debugging code too and run
it in a VM to see how those despicable things fare. But then I remove the
debugging glue again when cleaning up the despicable things and turning them
into proper patches.
So make this debugging code permanent but keep it out of reach from production
use and have it build- and boot-disabled by default.
Thx.
Borislav Petkov (AMD) (2):
x86/microcode: Add microcode= cmdline parsing
x86/microcode: Add microcode loader debugging functionality
.../admin-guide/kernel-parameters.txt | 15 +++-
arch/x86/Kconfig | 12 +++
arch/x86/kernel/cpu/microcode/amd.c | 88 ++++++++++++++-----
arch/x86/kernel/cpu/microcode/core.c | 55 ++++++++++--
arch/x86/kernel/cpu/microcode/internal.h | 10 +++
5 files changed, 149 insertions(+), 31 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-09 9:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 9:42 Borislav Petkov [this message]
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
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=20250809094206.28028-1-bp@kernel.org \
--to=bp@kernel.org \
--cc=bp@alien8.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.