On Wed, Jan 18, 2017 at 11:08 PM, Uros Bizjak wrote:
> On Wed, Jan 18, 2017 at 10:48 PM, Uros Bizjak wrote:
>> Hello!
>>
>>> This fix follows the same approach that glibc uses to disable TSX on
>>> processors on which it is broken. TSX can also be disabled through a
>>> microcode update on these
On Wed, Jan 18, 2017 at 10:48 PM, Uros Bizjak wrote:
> Hello!
>
>> This fix follows the same approach that glibc uses to disable TSX on
>> processors on which it is broken. TSX can also be disabled through a
>> microcode update on these processors, but glibc consensus is that it
>> cannot be dete
On Wed, Jan 18, 2017 at 10:48:28PM +0100, Uros Bizjak wrote:
> Hello!
>
> > This fix follows the same approach that glibc uses to disable TSX on
> > processors on which it is broken. TSX can also be disabled through a
> > microcode update on these processors, but glibc consensus is that it
> > ca
On Wed, Jan 18, 2017 at 10:48 PM, Uros Bizjak wrote:
> Hello!
>
>> This fix follows the same approach that glibc uses to disable TSX on
>> processors on which it is broken. TSX can also be disabled through a
>> microcode update on these processors, but glibc consensus is that it
>> cannot be dete
Hello!
> This fix follows the same approach that glibc uses to disable TSX on
> processors on which it is broken. TSX can also be disabled through a
> microcode update on these processors, but glibc consensus is that it
> cannot be detected reliably whether the microcode update has been
> applied
