From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] x86, microcode: Reloading fixes
Date: Sat, 6 Dec 2014 16:31:45 +0100 [thread overview]
Message-ID: <1417879908-4851-1-git-send-email-bp@alien8.de> (raw)
From: Borislav Petkov <bp@suse.de>
Hi guys,
please pull three fixes for the microcode loader. More specifically,
microcode reloading for 3.19. Patches are against tip/x86/microcode.
I have this also as a tag if you'd prefer to pull:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/microcode_fixes_for_3.19
This will have a conflict when merging into Linus' tree after
tip/x86/urgent has went in for 3.18 but resolving it should be easy. The
final result should be this with the ifdef dropped:
---
diff --git a/arch/x86/kernel/cpu/microcode/core.c b/arch/x86/kernel/cpu/microcode/core.c
index 08fe6e8a726e..15c29096136b 100644
--- a/arch/x86/kernel/cpu/microcode/core.c
+++ b/arch/x86/kernel/cpu/microcode/core.c
@@ -465,16 +465,8 @@ static void mc_bp_resume(void)
if (uci->valid && uci->mc)
microcode_ops->apply_microcode(cpu);
-#ifdef CONFIG_X86_64
else if (!uci->mc)
- /*
- * We might resume and not have applied late microcode but still
- * have a newer patch stashed from the early loader. We don't
- * have it in uci->mc so we have to load it the same way we're
- * applying patches early on the APs.
- */
- load_ucode_ap();
-#endif
+ reload_early_microcode();
}
--
Thanks.
Boris Ostrovsky (1):
x86, microcode: Don't initialize microcode code on paravirt
Borislav Petkov (2):
x86, microcode, intel: Drop unused parameter
x86, microcode: Reload microcode on resume
arch/x86/include/asm/microcode.h | 2 ++
arch/x86/include/asm/microcode_amd.h | 2 ++
arch/x86/include/asm/microcode_intel.h | 2 ++
arch/x86/kernel/cpu/microcode/amd_early.c | 18 +++++++++++
arch/x86/kernel/cpu/microcode/core.c | 10 ++----
arch/x86/kernel/cpu/microcode/core_early.c | 21 +++++++++++++
arch/x86/kernel/cpu/microcode/intel_early.c | 48 +++++++++++++++++++++++------
7 files changed, 85 insertions(+), 18 deletions(-)
--
2.0.0
next reply other threads:[~2014-12-06 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 15:31 Borislav Petkov [this message]
2014-12-06 15:31 ` [PATCH 1/3] x86, microcode, intel: Drop unused parameter Borislav Petkov
2014-12-06 15:31 ` [PATCH 2/3] x86, microcode: Don't initialize microcode code on paravirt Borislav Petkov
2014-12-06 15:31 ` [PATCH 3/3] x86, microcode: Reload microcode on resume Borislav Petkov
2014-12-08 9:27 ` [PATCH 0/3] x86, microcode: Reloading fixes Ingo Molnar
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=1417879908-4851-1-git-send-email-bp@alien8.de \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome