On Fri, 19 Sep 2014, Andy Lutomirski wrote:
> Can we change the ucode blob format for these firmwares so that old
> kernels won't apply them? I have no other good ideas. The trouble is
> that distros *should* push out the new ucode, but only if there's some
> guarantee that they'll only be applied early, never late.
All it takes is to rm the /lib/firmware/intel-ucode/<haswell f-m-s> files,
while not touching the microcode you will add to the early initramfs.
Anyway, if you want to fix this through the stable kernel updates:
The intel microcode driver does a "sanity check" pass over all cpus before
the update, attempting to locate the appropriate microcode. It is trivial
to add the following logic to it:
if cpu_has(hle) && cpuid_in_table(haswell_cpuids) { ignore the microcode }.
You don't even have to key on the current microcode revision, as we don't
know for sure it will be safe to update these processors again when the BIOS
force-enabled HLE anyway.
We can enhance the blacklist to only key on the old microcode that always
enables Intel TSX later, if this proves to be safe.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
