From: Ashok Raj <ashok.raj@intel.com>
To: Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: Tony Luck <tony.luck@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
"LKML Mailing List" <linux-kernel@vger.kernel.org>,
X86-kernel <x86@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ashok Raj <ashok.raj@intel.com>
Subject: [PATCH 0/5] Adding more robustness to microcode loading
Date: Sat, 13 Aug 2022 22:38:20 +0000 [thread overview]
Message-ID: <20220813223825.3164861-1-ashok.raj@intel.com> (raw)
Hi Boris and Thomas,
This is an attempt to move towards enabling late-load ON by default, and if
the taint flag can be removed after this patch series.
- Patch1: Documentation improvements. (to tainted-kernels.rst) and
x86/microcode.rst.
- Patch2: (Intel) Fix in patch-match during an update left the old patch still in
the list. This isn't necessary.
- Patch3: One key improvement is the addition of min_rev_id in the
microcode header. This allows a way for CPU microcode to declare itself
if this is suitable for late-loads.
- Patch4: Avoid any MCE's while a microcode update is in progress. This
basically promotes any arriving MCE's to shutdown automatically.
- Patch5: Protect the secondary thread from entering NMI before a microcode
update is complete in the primary thread.
Ashok Raj (5):
x86/microcode: Add missing documentation that late-load will taint
kernel
x86/microcode/intel: Check against CPU signature before saving
microcode
x86/microcode/intel: Allow a late-load only if a min rev is specified
x86/microcode: Avoid any chance of MCE's during microcode update
x86/microcode: Handle NMI's during microcode update.
Documentation/admin-guide/tainted-kernels.rst | 8 +-
Documentation/x86/microcode.rst | 95 +++++++++++++++++-
arch/x86/include/asm/mce.h | 4 +
arch/x86/include/asm/microcode_intel.h | 4 +-
arch/x86/kernel/cpu/mce/core.c | 9 ++
arch/x86/kernel/cpu/microcode/core.c | 99 ++++++++++++++++++-
arch/x86/kernel/cpu/microcode/intel.c | 34 ++++++-
7 files changed, 240 insertions(+), 13 deletions(-)
--
2.32.0
next reply other threads:[~2022-08-13 22:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 22:38 Ashok Raj [this message]
2022-08-13 22:38 ` [PATCH 1/5] x86/microcode: Add missing documentation that late-load will taint kernel Ashok Raj
2022-08-15 19:40 ` [tip: x86/microcode] x86/microcode: Document the whole late loading problem tip-bot2 for Ashok Raj
2022-08-16 3:21 ` Ashok Raj
2022-08-16 7:40 ` Borislav Petkov
2022-08-16 6:51 ` Ingo Molnar
2022-08-16 7:46 ` tip-bot2 for Ashok Raj
2022-08-18 14:04 ` tip-bot2 for Ashok Raj
2022-08-13 22:38 ` [PATCH 2/5] x86/microcode/intel: Check against CPU signature before saving microcode Ashok Raj
2022-08-13 22:38 ` [PATCH 3/5] x86/microcode/intel: Allow a late-load only if a min rev is specified Ashok Raj
2022-08-15 7:43 ` Peter Zijlstra
2022-08-15 12:29 ` Ashok Raj
2022-08-15 7:46 ` Peter Zijlstra
2022-08-15 12:41 ` Ashok Raj
2022-08-15 13:04 ` Peter Zijlstra
2022-08-18 17:34 ` Dave Hansen
2022-08-13 22:38 ` [PATCH 4/5] x86/microcode: Avoid any chance of MCE's during microcode update Ashok Raj
2022-08-13 22:38 ` [PATCH 5/5] x86/microcode: Handle NMI's " Ashok Raj
2022-08-14 0:13 ` Andy Lutomirski
2022-08-14 1:19 ` Andy Lutomirski
2022-08-14 3:05 ` Ashok Raj
2022-08-14 2:54 ` Ashok Raj
2022-08-14 11:58 ` Andrew Cooper
2022-08-14 14:41 ` Ashok Raj
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=20220813223825.3164861-1-ashok.raj@intel.com \
--to=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@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®