According to the latest microcode update from Intel (on Feb 8, 2018) on
Skylake we should be using the microcode revisions 0xC2***, so we need
to remove that from the blacklist now.
Signed-off-by: Darren Kenny <[email protected]>
Reviewed-by: Konrad Rzeszutek Wilk <[email protected]>
Tested-by: Konrad Rzeszutek Wilk <[email protected]>
---
arch/x86/kernel/cpu/intel.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
index 319bf98..276bfe2 100644
--- a/arch/x86/kernel/cpu/intel.c
+++ b/arch/x86/kernel/cpu/intel.c
@@ -123,8 +123,6 @@ static const struct sku_microcode spectre_bad_microcodes[] = {
{ INTEL_FAM6_KABYLAKE_MOBILE, 0x09, 0x84 },
{ INTEL_FAM6_SKYLAKE_X, 0x03, 0x0100013e },
{ INTEL_FAM6_SKYLAKE_X, 0x04, 0x0200003c },
- { INTEL_FAM6_SKYLAKE_MOBILE, 0x03, 0xc2 },
- { 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 },
--
2.9.5
On Fri, 2018-02-09 at 14:10 +0000, Darren Kenny wrote:
> According to the latest microcode update from Intel (on Feb 8, 2018) on
> Skylake we should be using the microcode revisions 0xC2***, so we need
> to remove that from the blacklist now.
The doc also suggests that Gemini Lake 0x22 is also now known to be OK.
I'll do a full pass over it and bring the list completely up to date.
Thanks.
On Fri, Feb 09, 2018 at 02:29:27PM +0000, David Woodhouse wrote:
>On Fri, 2018-02-09 at 14:10 +0000, Darren Kenny wrote:
>> According to the latest microcode update from Intel (on Feb 8, 2018) on
>> Skylake we should be using the microcode revisions 0xC2***, so we need
>> to remove that from the blacklist now.
>
>The doc also suggests that Gemini Lake 0x22 is also now known to be OK.
>I'll do a full pass over it and bring the list completely up to date.
>
>Thanks.
OK, let me know if you need me to do anything.
Thanks,
Darren.