From: Alexander Sergeyev <sergeev917@gmail.com>
To: David Woodhouse <dwmw@amazon.co.uk>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Kyle Huey <me@kylehuey.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: spectre v2 microcodes blacklist (march update)
Date: Sun, 4 Mar 2018 00:02:04 +0300 [thread overview]
Message-ID: <20180303210204.GA6148@localhost.localdomain> (raw)
Hi,
the microcode revision guidance from Intel is revised once again [1] (1 Mar).
It looks like the following:
>Intel document only clears the 0xc2 microcode on *some* parts with CPUID 506E3
>(INTEL_FAM6_SKYLAKE_DESKTOP stepping 3). For the Skylake H/S platform it's OK
>but for Skylake E3 which has the same CPUID it isn't (yet) cleared.
is no longer a problem. CPUID 506E3 with both Skylake H/S and Skylake Xeon E3
is labelled as "production" now.
Could we drop { INTEL_FAM6_SKYLAKE_DESKTOP, 0x03, 0xc2 } from
spectre_bad_microcodes?
[1]
https://newsroom.intel.com/wp-content/uploads/sites/11/2018/03/microcode-update-guidance.pdf
next reply other threads:[~2018-03-03 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 21:02 Alexander Sergeyev [this message]
2018-03-05 9:17 ` 王金浦
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=20180303210204.GA6148@localhost.localdomain \
--to=sergeev917@gmail.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kylehuey.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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®