This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Intel microcode update and glibc HLE
- From: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: Siddhesh Poyarekar <siddhesh at redhat dot com>, Josh Boyer <jwboyer at fedoraproject dot org>, Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>, libc-alpha <libc-alpha at sourceware dot org>, Kyle McMartin <kmcmarti at redhat dot com>
- Date: Sat, 27 Sep 2014 10:44:44 +0530
- Subject: Re: Intel microcode update and glibc HLE
- Authentication-results: sourceware.org; auth=none
- References: <20140926180900 dot GW1716 at spoyarek dot pnq dot redhat dot com> <CA+5PVA5MVA+ZoLBObWgkmsi1JTj6SkFL+q6OnTLALxm2PnJ6Qw at mail dot gmail dot com> <20140926185440 dot GX1716 at spoyarek dot pnq dot redhat dot com> <542646B5 dot 6050103 at redhat dot com>
On 27 September 2014 10:40, Carlos O'Donell <carlos@redhat.com> wrote:
> It turns out to be more than just a configure flag.
>
> Andi's recent rwlock changes use TSX unconditionally.
I would reckon that it's wrong to do so. Not using
--enable-lock-elision should disable all elision code.
> I've raised this issue with Andi to see if we can put it all under the
> same configure flag.
>
> Similarly for ppc64 and s390 I think I'll make the flag do this:
>
> --enable-lock-elision=yes (enable for all machines)
> --enable-lock-elisoin=x86_64,ppc64,s390x (enable for these machines)
Why do you need this? Wouldn't it be sufficient to do this in
distribution spec files?
Siddhesh
--
http://siddhesh.in