From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/glibc: enable lock elision on x86_64 hosts
Date: Sun, 19 Jul 2015 11:23:14 +0200 [thread overview]
Message-ID: <20150719112314.2d733eaf@free-electrons.com> (raw)
In-Reply-To: <1426716071-27570-2-git-send-email-steven@uplinklabs.net>
Dear Steven Noonan,
On Wed, 18 Mar 2015 15:01:09 -0700, Steven Noonan wrote:
> Signed-off-by: Steven Noonan <steven@uplinklabs.net>
> ---
> package/glibc/glibc.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
> index 0a37bb3..651711a 100644
> --- a/package/glibc/glibc.mk
> +++ b/package/glibc/glibc.mk
> @@ -90,6 +90,7 @@ define GLIBC_CONFIGURE_CMDS
> --prefix=/usr \
> --enable-shared \
> $(if $(BR2_SOFT_FLOAT),--without-fp,--with-fp) \
> + $(if $(BR2_x86_64),--enable-lock-elision,) \
What happens on x86-64 processors that don't have the HW support needed
for lock elision ? Does glibc gracefully falls back at runtime to
"normal" locks ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-19 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 22:01 [Buildroot] [PATCH 1/3] arch: add corei7-avx Steven Noonan
2015-03-18 22:01 ` [Buildroot] [PATCH] package/glibc: enable lock elision on x86_64 hosts Steven Noonan
2015-07-19 9:23 ` Thomas Petazzoni [this message]
2015-07-19 9:33 ` Baruch Siach
2015-07-20 20:57 ` Thomas Petazzoni
2015-03-18 22:01 ` [Buildroot] [PATCH 2/3] arch: add core-avx2 Steven Noonan
2015-04-09 20:19 ` Gustavo Zacarias
2015-03-18 22:01 ` [Buildroot] [PATCH 3/3] packages: add AVX/AVX2 support to ffmpeg/opencv Steven Noonan
2015-04-09 20:16 ` [Buildroot] [PATCH 1/3] arch: add corei7-avx Gustavo Zacarias
2015-04-09 21:35 ` Thomas Petazzoni
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=20150719112314.2d733eaf@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.