All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH] x86/microcode/AMD: Document which patches are not released for late loading
Date: Sat, 15 Apr 2023 16:28:21 +0200	[thread overview]
Message-ID: <20230415142821.24725-1-bp@alien8.de> (raw)

From: "Borislav Petkov (AMD)" <bp@alien8.de>

PeterZ wanted this spelled out explicitly. Add it to the documentation
so that everyone's on the same page wrt to which microcode patches are
not allowed to be late loaded.

Suggested-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
---
 Documentation/x86/microcode.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/x86/microcode.rst b/Documentation/x86/microcode.rst
index 15b52e2b181d..d5ef9184030c 100644
--- a/Documentation/x86/microcode.rst
+++ b/Documentation/x86/microcode.rst
@@ -218,6 +218,10 @@ a fault happens, the whole core will see it either before the microcode
 patch has been applied or after. In either case, T0 and T1 will have the
 same microcode revision and nothing intermediate.
 
+In addition, microcode patches which modify software-visible features
+like CPUID bits, MSRs, chicken bits, etc are not released for late
+loading.
+
 Builtin microcode
 =================
 
-- 
2.35.1


             reply	other threads:[~2023-04-15 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15 14:28 Borislav Petkov [this message]
2023-04-17 13:46 ` [tip: x86/microcode] x86/microcode/AMD: Document which patches are not released for late loading tip-bot2 for Borislav Petkov (AMD)
2023-04-21 22:33 ` [PATCH] " Thomas Gleixner

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=20230415142821.24725-1-bp@alien8.de \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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.