From: tip-bot for Alexander Sergeyev <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: qianyue.zj@alibaba-inc.com, tglx@linutronix.de, mingo@kernel.org,
linux-kernel@vger.kernel.org, sergeev917@gmail.com,
hpa@zytor.com, dwmw@amazon.co.uk, gregkh@linuxfoundation.org,
me@kylehuey.com
Subject: [tip:x86/pti] x86/speculation: Remove Skylake C2 from Speculation Control microcode blacklist
Date: Fri, 16 Mar 2018 04:55:12 -0700 [thread overview]
Message-ID: <tip-e3b3121fa8da94cb20f9e0c64ab7981ae47fd085@git.kernel.org> (raw)
In-Reply-To: <20180313193856.GA8580@localhost.localdomain>
Commit-ID: e3b3121fa8da94cb20f9e0c64ab7981ae47fd085
Gitweb: https://git.kernel.org/tip/e3b3121fa8da94cb20f9e0c64ab7981ae47fd085
Author: Alexander Sergeyev <sergeev917@gmail.com>
AuthorDate: Tue, 13 Mar 2018 22:38:56 +0300
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Fri, 16 Mar 2018 12:33:11 +0100
x86/speculation: Remove Skylake C2 from Speculation Control microcode blacklist
In accordance with Intel's microcode revision guidance from March 6 MCU
rev 0xc2 is cleared on both Skylake H/S and Skylake Xeon E3 processors
that share CPUID 506E3.
Signed-off-by: Alexander Sergeyev <sergeev917@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Jia Zhang <qianyue.zj@alibaba-inc.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kyle Huey <me@kylehuey.com>
Cc: David Woodhouse <dwmw@amazon.co.uk>
Link: https://lkml.kernel.org/r/20180313193856.GA8580@localhost.localdomain
---
arch/x86/kernel/cpu/intel.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
index 4aa9fd379390..c3af167d0a70 100644
--- a/arch/x86/kernel/cpu/intel.c
+++ b/arch/x86/kernel/cpu/intel.c
@@ -105,7 +105,7 @@ static void probe_xeon_phi_r3mwait(struct cpuinfo_x86 *c)
/*
* Early microcode releases for the Spectre v2 mitigation were broken.
* Information taken from;
- * - https://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf
+ * - https://newsroom.intel.com/wp-content/uploads/sites/11/2018/03/microcode-update-guidance.pdf
* - https://kb.vmware.com/s/article/52345
* - Microcode revisions observed in the wild
* - Release note from 20180108 microcode release
@@ -123,7 +123,6 @@ static const struct sku_microcode spectre_bad_microcodes[] = {
{ INTEL_FAM6_KABYLAKE_MOBILE, 0x09, 0x80 },
{ INTEL_FAM6_SKYLAKE_X, 0x03, 0x0100013e },
{ INTEL_FAM6_SKYLAKE_X, 0x04, 0x0200003c },
- { INTEL_FAM6_SKYLAKE_DESKTOP, 0x03, 0xc2 },
{ INTEL_FAM6_BROADWELL_CORE, 0x04, 0x28 },
{ INTEL_FAM6_BROADWELL_GT3E, 0x01, 0x1b },
{ INTEL_FAM6_BROADWELL_XEON_D, 0x02, 0x14 },
prev parent reply other threads:[~2018-03-16 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 19:38 [PATCH] x86/speculation: Remove Skylake C2 from Speculation Control microcode blacklist Alexander Sergeyev
2018-03-16 11:55 ` tip-bot for Alexander Sergeyev [this message]
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=tip-e3b3121fa8da94cb20f9e0c64ab7981ae47fd085@git.kernel.org \
--to=tipbot@zytor.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=me@kylehuey.com \
--cc=mingo@kernel.org \
--cc=qianyue.zj@alibaba-inc.com \
--cc=sergeev917@gmail.com \
--cc=tglx@linutronix.de \
/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.