Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sun, 4 Mar 2018 00:02:04 +0300
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)
Message-ID: <20180303210204.GA6148@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
User-Agent: mtt
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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