[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140919110014.GC29639@khazad-dum.debian.net>
Date: Fri, 19 Sep 2014 08:00:15 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Andy Lutomirski <luto@...capital.net>
Cc: Borislav Petkov <bp@...en8.de>,
Chuck Ebbert <cebbert.lkml@...il.com>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: x86, microcode: BUG: microcode update that changes x86_capability
On Thu, 18 Sep 2014, Andy Lutomirski wrote:
> On Sep 18, 2014 5:13 PM, "Henrique de Moraes Holschuh" <hmh@....eng.br> wrote:
> > Here's a plan that might work, pending actually checking the libpthread TSX
> > code to make sure it keys on /proc/cpuinfo flags:
>
> Surely it checks cpuid directly, though.
Unfortunately, you're correct. It uses cpuid() directly. So, my plan is
not going to work.
> Can we twiddle the cpuid bit? I never noticed any way in the docs to
No, we can't, at least not by manipulating cpuid itself.
And if the old microcode had such a Intel TSX on/off switch (which would
also reset the bit), the "fix" that disables Intel TSX should have been a
BIOS update, not a microcode update... so I consider that very unlikely.
I'm filling a bug on Debian glibc, asking them to blacklist HLE until
further notice.
So that's two nice features that might go the way of the Dodo over this:
We're also killing microcode update support outside of the initramfs in
Debian. It has become obvious that anything other than the early initramfs
method of microcode updates should be considered a developer thing.
--
"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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists