Re: update spectre v2 microcodes blacklist

2018-02-12 Thread Alexander Sergeyev
+{ INTEL_FAM6_BROADWELL_X,0x01, 0x0b23 }, That's redundant since blacklisting 0x0b25 will also stop us from using 0x0b23 anyway. and 23 is the pre security version so known good. But 0x0b23 is listed under "stop deploying these MCU revs" (page 4, row 4). Has something

RE: update spectre v2 microcodes blacklist

2018-02-12 Thread Van De Ven, Arjan
> > 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, 0x0b23 }, > >  { INTEL_FAM6_BROADWELL_X,0x01,

Re: update spectre v2 microcodes blacklist

2018-02-12 Thread David Woodhouse
On Sat, 2018-02-10 at 20:14 +0300, Alexander Sergeyev wrote: > > > > 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

Re: update spectre v2 microcodes blacklist

2018-02-10 Thread Alexander Sergeyev
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