public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>,
	Josh Boyer <jwboyer@fedoraproject.org>,
	Adhemerval Zanella <azanella@linux.vnet.ibm.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
	Kyle McMartin <kmcmarti@redhat.com>
Subject: Re: Intel microcode update and glibc HLE
Date: Sat, 27 Sep 2014 05:10:00 -0000	[thread overview]
Message-ID: <542646B5.6050103@redhat.com> (raw)
In-Reply-To: <20140926185440.GX1716@spoyarek.pnq.redhat.com>

On 09/26/2014 02:54 PM, Siddhesh Poyarekar wrote:
>> I'll be updating the Fedora kernel and dracut to do early microcode
>> loading today.  Kyle McMartin looked at the suspend/hibernate-resume
>> paths and things should work fine with early microcode loading.
> 
> That's great.

I agree, that is great news.
 
>> Disabling this in glibc on x86 seems fine since nothing will be
>> capable of using it until newer CPUs are released, but it wasn't
>> strictly necessary.
> 
> I wasn't aware of the plan to do the early microcode loading, which is
> why we went with disabling HLE.  It's really just a flip of a
> configure flag and rebuild, so we can even revert it and test once the
> kernel bits are in.

It turns out to be more than just a configure flag.

Andi's recent rwlock changes use TSX unconditionally.

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)
--enable-lock-elision-no (disable for all machines)

Cheers,
Carlos.

  reply	other threads:[~2014-09-27  5:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 18:09 Siddhesh Poyarekar
2014-09-26 18:19 ` Adhemerval Zanella
2014-09-26 18:57   ` Siddhesh Poyarekar
2014-09-26 18:28 ` Josh Boyer
2014-09-26 18:54   ` Siddhesh Poyarekar
2014-09-27  5:10     ` Carlos O'Donell [this message]
2014-09-27  5:11       ` Carlos O'Donell
2014-09-27  5:14       ` Siddhesh Poyarekar
2014-09-27  5:26         ` Roland McGrath
2014-09-27  5:39         ` Carlos O'Donell
2014-09-27  7:37       ` Andreas Schwab
2014-09-27 16:26         ` Carlos O'Donell

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=542646B5.6050103@redhat.com \
    --to=carlos@redhat.com \
    --cc=azanella@linux.vnet.ibm.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=kmcmarti@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).