From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>
Subject: [PATCH v4 0/4] Prevent attempting updates known to fail
Date: Thu, 22 Jun 2023 18:42:15 +0100 [thread overview]
Message-ID: <20230622174219.8871-1-alejandro.vallejo@cloud.com> (raw)
v4:
* The refactor Andrew asked for to avoid a conditional check on
early_microcode_init(). I'm not convinced it's clearer, but it's not
much more complicated either, so I don't mind.
* Removed microcode_ops builders in favour of a separate Intel-specific
function to check whether the system can load new microcode. This keeps
the static structs in the right sections.
Under certain conditions a CPU may not be able to perform microcode updates
even if hardware exists to that effect. In particular:
* If Xen runs under certain hypervisors they won't allow microcode
updates, and will signal this fact by reporting a microcode revision of
-1.
* If the DIS_MCU_LOAD bit is set, which is expected in some baremetal
clouds where the owner may not trust the tenant, then the CPU is not
capable of loading new microcode.
This series adds logic so that in both of these cases we don't needlessly
attempt updates that are not going to succeed. Patch summary:
Patch 1 Introduces the logic to print the microcode revision if at all
possible
Patch 2 Ignores microcode facilities when the current microcode revision is -1
Patch 3 Moves the MSR_ARCH_CAPS read in tsx_init() to early_cpu_init() and
early_microcode_init()
Patch 4 Adds the logic to detect microcode updates being disabled on Intel.
Alejandro Vallejo (4):
x86/microcode: Allow reading microcode revision even if it can't be
updated
x86/microcode: Ignore microcode loading interface for revision = -1
x86: Read MSR_ARCH_CAPS immediately after early_microcode_init()
x86/microcode: Disable microcode update handler if DIS_MCU_UPDATE is
set
xen/arch/x86/cpu/common.c | 5 ++++
xen/arch/x86/cpu/microcode/core.c | 41 +++++++++++++++++++++++----
xen/arch/x86/cpu/microcode/intel.c | 13 +++++++++
xen/arch/x86/cpu/microcode/private.h | 7 +++++
xen/arch/x86/include/asm/cpufeature.h | 1 +
xen/arch/x86/include/asm/msr-index.h | 5 ++++
xen/arch/x86/tsx.c | 16 +++--------
7 files changed, 70 insertions(+), 18 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-22 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 17:42 Alejandro Vallejo [this message]
2023-06-22 17:42 ` [PATCH v4 1/4] x86/microcode: Allow reading microcode revision even if it can't be updated Alejandro Vallejo
2023-06-22 17:42 ` [PATCH v4 2/4] x86/microcode: Ignore microcode loading interface for revision = -1 Alejandro Vallejo
2023-06-23 7:27 ` Jan Beulich
2023-06-22 17:42 ` [PATCH v4 3/4] x86: Read MSR_ARCH_CAPS immediately after early_microcode_init() Alejandro Vallejo
2023-06-23 7:33 ` Jan Beulich
2023-06-29 15:02 ` Alejandro Vallejo
2023-06-22 17:42 ` [PATCH v4 4/4] x86/microcode: Disable microcode update handler if DIS_MCU_UPDATE is set Alejandro Vallejo
2023-06-23 7:39 ` Jan Beulich
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=20230622174219.8871-1-alejandro.vallejo@cloud.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.