From: Ashok Raj <ashok.raj@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: X86-kernel <x86@kernel.org>,
LKML Mailing List <linux-kernel@vger.kernel.org>,
Ashok Raj <ashok.raj@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Tony Luck <tony.luck@intel.com>,
alison.schofield@intel.com, reinette.chatre@intel.com
Subject: [Patch V1 0/7] x86/microcode: Some cleanups and fixes for microcode
Date: Tue, 29 Nov 2022 13:08:25 -0800 [thread overview]
Message-ID: <20221129210832.107850-1-ashok.raj@intel.com> (raw)
Hi Boris
These are based on tip/x86/microcode after the recent IFS merge.
As discussed in IRC, feel free to massage/rework/re-organize them in a way
that you intend to see them.
Patch1: Fixes a minor race in pr_info due to a recent change in
microcode_init() sequence.
Patch2: Remove microcode apply retries that cause a hang when loading
fails.
Patch3: Prep patch for patch4, since its only used in core.c make it local
there.
Patch4: Take a snapshot of x86 features before and after microcode update,
instead of using the one from boot_cpu already cached.
Patch5: prepare early print to simplify patch 6 and 7.
Patch6: Print old and new rev after early loading. Its useful to know what
BIOS version of the patchrev was.
Patch7: Print a message when early loading fails. Currently there is no
message to user.
Ashok Raj (7):
x86/microcode/intel: Remove redundant microcode rev pr_info()s
x86/microcode/intel: Remove retries on early microcode load
x86/microcode/core: Move microcode_check() to cpu/microcode/core.c
x86/microcode/core: Take a snapshot before and after applying
microcode
x86/microcode/intel: Prepare the print_ucode_rev to simply take a rev
to print
x86/microcode/intel: Print old and new rev during early boot
x86/microcode/intel: Print when early microcode loading fails
arch/x86/include/asm/processor.h | 3 +-
arch/x86/kernel/cpu/cpu.h | 1 -
arch/x86/kernel/cpu/common.c | 32 -------------
arch/x86/kernel/cpu/microcode/core.c | 49 +++++++++++++++++++-
arch/x86/kernel/cpu/microcode/intel.c | 67 +++++++++++----------------
5 files changed, 75 insertions(+), 77 deletions(-)
base-commit: 1a63b58082869273bfbab1b945007193f7bd3a78
--
2.34.1
next reply other threads:[~2022-11-29 21:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 21:08 Ashok Raj [this message]
2022-11-29 21:08 ` [Patch V1 1/7] x86/microcode/intel: Remove redundant microcode rev pr_info()s Ashok Raj
2022-12-02 18:58 ` Thomas Gleixner
2022-12-03 0:26 ` Ashok Raj
2022-12-03 13:42 ` Borislav Petkov
2022-11-29 21:08 ` [Patch V1 2/7] x86/microcode/intel: Remove retries on early microcode load Ashok Raj
2022-12-02 19:01 ` Thomas Gleixner
2022-12-03 1:48 ` Ashok Raj
2022-12-02 23:53 ` Sohil Mehta
2022-12-03 1:47 ` Ashok Raj
2022-12-05 12:18 ` Borislav Petkov
2022-12-05 16:42 ` Ashok Raj
2022-12-05 20:53 ` [tip: x86/microcode] x86/microcode/intel: Do not retry microcode reloading on the APs tip-bot2 for Ashok Raj
2022-11-29 21:08 ` [Patch V1 3/7] x86/microcode/core: Move microcode_check() to cpu/microcode/core.c Ashok Raj
2022-12-02 19:02 ` Thomas Gleixner
2022-12-02 20:57 ` Sohil Mehta
2022-12-03 0:21 ` Ashok Raj
2022-12-05 16:25 ` Borislav Petkov
2022-12-05 17:05 ` Ashok Raj
2022-12-05 21:27 ` Borislav Petkov
2022-11-29 21:08 ` [Patch V1 4/7] x86/microcode/core: Take a snapshot before and after applying microcode Ashok Raj
2022-12-02 19:09 ` Thomas Gleixner
2022-12-03 1:57 ` Ashok Raj
2022-12-07 20:25 ` Borislav Petkov
2022-12-08 0:05 ` Ashok Raj
2022-11-29 21:08 ` [Patch V1 5/7] x86/microcode/intel: Prepare the print_ucode_rev to simply take a rev to print Ashok Raj
2022-12-02 19:23 ` Thomas Gleixner
2022-11-29 21:08 ` [Patch V1 6/7] x86/microcode/intel: Print old and new rev during early boot Ashok Raj
2022-12-02 19:29 ` Thomas Gleixner
2022-11-29 21:08 ` [Patch V1 7/7] x86/microcode/intel: Print when early microcode loading fails Ashok Raj
2022-12-02 19:30 ` Thomas Gleixner
2022-12-05 18:19 ` 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=20221129210832.107850-1-ashok.raj@intel.com \
--to=ashok.raj@intel.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.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®