From: Ashok Raj <ashok.raj@intel.com>
To: Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.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>
Subject: [PATCH v2 0/6] Some fixes and cleanups for microcode
Date: Tue, 27 Dec 2022 11:23:34 -0800 [thread overview]
Message-ID: <20221227192340.8358-1-ashok.raj@intel.com> (raw)
Hi Boris
This is a followup after earlier post [1]
First 2 patches have been merged, sending the rest of the patches after
addressing comments and adding Thomas's reviewed by.
Please review and consider applying.
Changes since last post.
v2:
- Updated commit logs as suggested by Thomas and Boris
- Added Reviewed-by Thomas, and Tony
[1]https://lore.kernel.org/lkml/20221129210832.107850-1-ashok.raj@intel.com/
Cheers,
Ashok
Ashok Raj (6):
x86/microcode/core: Move microcode_check() to cpu/microcode/core.c
x86/microcode/core: Take a snapshot before and after applying
microcode
x86/microcode: Display revisions only when update is successful
x86/microcode/intel: Use a plain revision argument for
print_ucode_rev()
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 | 62 +++++++++++++++++++++++++--
arch/x86/kernel/cpu/microcode/intel.c | 52 +++++++++++-----------
5 files changed, 83 insertions(+), 67 deletions(-)
base-commit: 1b929c02afd37871d5afb9d498426f83432e71c2
--
2.34.1
next reply other threads:[~2022-12-27 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 19:23 Ashok Raj [this message]
2022-12-27 19:23 ` [PATCH v2 1/6] x86/microcode/core: Move microcode_check() to cpu/microcode/core.c Ashok Raj
2022-12-27 19:50 ` Borislav Petkov
2022-12-27 19:59 ` Ashok Raj
2022-12-27 21:01 ` [PATCH v3 1/2] x86/microcode: Add a parameter to microcode_check() to store CPU capabilities Ashok Raj
2022-12-27 21:01 ` [PATCH v3 2/2] x86/microcode/core: Take a snapshot before and after applying microcode Ashok Raj
2022-12-28 18:36 ` Ashok Raj
2022-12-27 19:23 ` [PATCH v2 2/6] " Ashok Raj
2022-12-27 19:23 ` [PATCH v2 3/6] x86/microcode: Display revisions only when update is successful Ashok Raj
2022-12-27 19:23 ` [PATCH v2 4/6] x86/microcode/intel: Use a plain revision argument for print_ucode_rev() Ashok Raj
2022-12-27 19:23 ` [PATCH v2 5/6] x86/microcode/intel: Print old and new rev during early boot Ashok Raj
2022-12-27 19:23 ` [PATCH v2 6/6] x86/microcode/intel: Print when early microcode loading fails 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=20221227192340.8358-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=tglx@linutronix.de \
--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®