From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Borislav Petkov <bp@alien8.de>,
Chuck Ebbert <cebbert.lkml@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: x86, microcode: BUG: microcode update that changes x86_capability
Date: Thu, 18 Sep 2014 17:28:08 -0700 [thread overview]
Message-ID: <713c7342-bdf4-4e38-8de2-37d840d7028b@email.android.com> (raw)
In-Reply-To: <CALCETrVoeqQUXH7g+reu=hUvCJoiy+edHKBqYKPWXPCS3_UtUw@mail.gmail.com>
The cpuid bit gets twiddled...
On September 18, 2014 5:23:40 PM PDT, Andy Lutomirski <luto@amacapital.net> wrote:
>On Sep 18, 2014 5:13 PM, "Henrique de Moraes Holschuh" <hmh@hmh.eng.br>
>wrote:
>>
>> On Thu, 18 Sep 2014, Henrique de Moraes Holschuh wrote:
>> > On Thu, 18 Sep 2014, H. Peter Anvin wrote:
>> > > We should, but this is also part of why we want the early ucode
>capability.
>> >
>> > Well, yes. But that won't help the several stable and LTS distros
>with
>> > kernels without early ucode update support.
>>
>> 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.
>
>Can we twiddle the cpuid bit? I never noticed any way in the docs to
>do it, but if BIOS has such an ability, maybe we do, too. I wonder if
>there's anything semi-documented in biosbits, or if we could just
>reverse-engineer it.
>
>--Andy
>
>>
>> Add a cpu quirk, triggered by the Haswell cpuids, to force-disable
>hle on
>> the affected processors.
>>
>> This will work around the x86_capability capability issue (which
>should
>> still be fixed, anyway), and it should also get userspace to stay
>away from
>> TSX, therefore also working around the worst issue (processes getting
>> SIGILL).
>>
>> This will disable the "user may ask the BIOS to keep TSX enabled"
>> anti-feature, though. This drawback can be avoided, but only if a
>future
>> microcode update won't re-disable hle when the BIOS enabled it. For
>now, I
>> suggest that we decree that "hle is toast" for the current Haswells
>and add
>> back ways to enable it for testing when we know more about it.
>>
>> --
>> "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
--
Sent from my mobile phone. Please pardon brevity and lack of formatting.
next prev parent reply other threads:[~2014-09-19 0:28 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 13:52 x86, microcode: BUG: microcode update that changes x86_capability Henrique de Moraes Holschuh
2014-09-18 19:14 ` Andy Lutomirski
2014-09-18 19:53 ` Chuck Ebbert
2014-09-18 19:55 ` H. Peter Anvin
2014-09-18 20:06 ` Henrique de Moraes Holschuh
2014-09-19 0:13 ` Henrique de Moraes Holschuh
2014-09-19 0:23 ` Andy Lutomirski
2014-09-19 0:28 ` H. Peter Anvin [this message]
2014-09-19 1:00 ` Andy Lutomirski
2014-09-19 8:03 ` Borislav Petkov
2014-09-19 11:00 ` Henrique de Moraes Holschuh
2014-09-19 11:29 ` Borislav Petkov
2014-09-19 12:54 ` Chuck Ebbert
2014-09-19 13:14 ` Josh Boyer
2014-09-19 13:37 ` Chuck Ebbert
2014-09-19 15:00 ` Borislav Petkov
2014-09-19 16:13 ` Andy Lutomirski
2014-09-19 16:54 ` Henrique de Moraes Holschuh
2014-09-19 16:42 ` Henrique de Moraes Holschuh
2014-09-23 20:00 ` Borislav Petkov
2014-09-24 14:56 ` Henrique de Moraes Holschuh
2014-09-24 15:00 ` Andy Lutomirski
2014-09-24 17:45 ` Henrique de Moraes Holschuh
2014-09-24 17:48 ` Andy Lutomirski
2014-09-24 18:59 ` Henrique de Moraes Holschuh
2014-09-24 19:34 ` Andy Lutomirski
2014-09-25 8:57 ` Borislav Petkov
2014-09-25 8:51 ` Borislav Petkov
2014-09-25 11:36 ` Henrique de Moraes Holschuh
2014-09-25 12:10 ` Borislav Petkov
2014-09-25 14:40 ` Henrique de Moraes Holschuh
2014-09-25 14:56 ` Borislav Petkov
2014-09-25 15:30 ` Henrique de Moraes Holschuh
2014-09-25 15:50 ` Borislav Petkov
2014-09-25 16:41 ` Henrique de Moraes Holschuh
2014-09-25 16:57 ` Borislav Petkov
2014-09-25 17:09 ` Henrique de Moraes Holschuh
2014-09-19 13:51 ` Henrique de Moraes Holschuh
2014-09-19 14:49 ` Borislav Petkov
2014-09-19 17:22 ` Henrique de Moraes Holschuh
2014-09-19 22:35 ` Henrique de Moraes Holschuh
2014-09-29 11:51 ` Henrique de Moraes Holschuh
2014-09-19 9:56 ` Henrique de Moraes Holschuh
2014-09-19 16:11 ` Henrique de Moraes Holschuh
2014-09-22 0:37 ` Andi Kleen
2014-09-22 0:51 ` H. Peter Anvin
2014-09-22 0:58 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=713c7342-bdf4-4e38-8de2-37d840d7028b@email.android.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=cebbert.lkml@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).