From: Alexander Sergeyev <sergeev917@gmail.com>
To: David Woodhouse <dwmw@amazon.co.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Kyle Huey <me@kylehuey.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: update spectre v2 microcodes blacklist
Date: Sat, 10 Feb 2018 20:14:59 +0300 [thread overview]
Message-ID: <20180210171459.GA12797@localhost.localdomain> (raw)
In-Reply-To: <20180210123123.GA19396@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
>I didn't fully match the updated revision guidance and spectre_bad_microcodes
I compared these lists and it seems that the only difference is about skylakes.
Everything else is covered by less-or-equal criteria on revision version.
Both desktop and mobile skylakes are stated to be unaffected for 0xC2:
{ INTEL_FAM6_SKYLAKE_DESKTOP, 0x03, 0xc2 }, // signature 0x000506E3
{ INTEL_FAM6_SKYLAKE_MOBILE, 0x03, 0xc2 }, // signature 0x000406E3
I reformated the Intel bulletin into json format for ease of automation and
batch processing -- it is attached.
Raw diff between the mainline blacklist and the bulletin looks like:
@@ -1,5 +1,6 @@
{ INTEL_FAM6_BROADWELL_CORE, 0x04, 0x28 },
{ INTEL_FAM6_BROADWELL_GT3E, 0x01, 0x1b },
+{ INTEL_FAM6_BROADWELL_X, 0x01, 0x0b000023 },
{ INTEL_FAM6_BROADWELL_X, 0x01, 0x0b000025 },
{ INTEL_FAM6_BROADWELL_XEON_D, 0x02, 0x14 },
{ INTEL_FAM6_BROADWELL_XEON_D, 0x03, 0x07000011 },
@@ -9,12 +10,10 @@
{ INTEL_FAM6_HASWELL_X, 0x02, 0x3b },
{ INTEL_FAM6_HASWELL_X, 0x04, 0x10 },
{ INTEL_FAM6_IVYBRIDGE_X, 0x04, 0x42a },
-{ INTEL_FAM6_KABYLAKE_DESKTOP, 0x09, 0x84 },
-{ INTEL_FAM6_KABYLAKE_DESKTOP, 0x0a, 0x84 },
-{ INTEL_FAM6_KABYLAKE_DESKTOP, 0x0b, 0x84 },
-{ INTEL_FAM6_KABYLAKE_MOBILE, 0x09, 0x84 },
-{ INTEL_FAM6_KABYLAKE_MOBILE, 0x0a, 0x84 },
-{ INTEL_FAM6_SKYLAKE_DESKTOP, 0x03, 0xc2 },
-{ INTEL_FAM6_SKYLAKE_MOBILE, 0x03, 0xc2 },
-{ INTEL_FAM6_SKYLAKE_X, 0x03, 0x0100013e },
+{ INTEL_FAM6_KABYLAKE_DESKTOP, 0x09, 0x80 },
+{ INTEL_FAM6_KABYLAKE_DESKTOP, 0x0a, 0x80 },
+{ INTEL_FAM6_KABYLAKE_DESKTOP, 0x0b, 0x80 },
+{ INTEL_FAM6_KABYLAKE_MOBILE, 0x09, 0x80 },
+{ INTEL_FAM6_KABYLAKE_MOBILE, 0x0a, 0x80 },
+{ INTEL_FAM6_SKYLAKE_X, 0x04, 0x0200003a },
{ INTEL_FAM6_SKYLAKE_X, 0x04, 0x0200003c },
Note: Gemini Lake and Sandy Bridge are not considered (observed in wild).
[-- Attachment #2: microcode-update-guidance.json --]
[-- Type: application/json, Size: 34851 bytes --]
next prev parent reply other threads:[~2018-02-10 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 12:31 update spectre v2 microcodes blacklist Alexander Sergeyev
2018-02-10 17:14 ` Alexander Sergeyev [this message]
2018-02-12 9:34 ` David Woodhouse
2018-02-12 13:56 ` Van De Ven, Arjan
2018-02-12 14:11 ` Alexander Sergeyev
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=20180210171459.GA12797@localhost.localdomain \
--to=sergeev917@gmail.com \
--cc=alexander.levin@verizon.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