From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ed Maste <emaste@freebsd.org>, qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-thread: add TLS wrappers
Date: Mon, 01 Jul 2013 13:30:09 -0700 [thread overview]
Message-ID: <51D1E6D1.9070505@twiddle.net> (raw)
In-Reply-To: <CAFEAcA8K9m62XqYB-RQtLQpaO8a3nqn+hVzyKCwNXFADZjj9=A@mail.gmail.com>
On 07/01/2013 12:25 PM, Peter Maydell wrote:
> Does any OS have a __thread which compiles but is broken, or can
> we just have a configure test for this? That would let MacOSX+clang
> use __thread.
I suspect that this will work. Some targets may succeed in using gcc's
"emutls" path, which while slower than TLS is pretty much exactly the pthread
get/setcontext fallback that's been proposed elsewhere on this list.
r~
next prev parent reply other threads:[~2013-07-01 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 9:35 [Qemu-devel] [PATCH 0/2] Fast Thread-Local Storage support Stefan Hajnoczi
2013-07-01 9:35 ` [Qemu-devel] [PATCH 1/2] exec: do not use qemu/tls.h Stefan Hajnoczi
2013-07-01 9:51 ` Peter Maydell
2013-07-01 10:15 ` Paolo Bonzini
2013-07-01 10:47 ` Andreas Färber
2013-07-01 9:35 ` [Qemu-devel] [PATCH 2/2] qemu-thread: add TLS wrappers Stefan Hajnoczi
2013-07-01 9:54 ` Peter Maydell
2013-07-01 10:14 ` Paolo Bonzini
2013-07-04 16:27 ` Jan Kiszka
2013-07-04 16:38 ` Paolo Bonzini
2013-07-01 12:34 ` Stefan Hajnoczi
2013-07-01 18:52 ` Ed Maste
2013-07-01 19:25 ` Peter Maydell
2013-07-01 20:00 ` Ed Maste
2013-07-01 20:30 ` Richard Henderson [this message]
2013-07-02 7:54 ` Paolo Bonzini
2013-07-02 7:50 ` Stefan Hajnoczi
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=51D1E6D1.9070505@twiddle.net \
--to=rth@twiddle.net \
--cc=emaste@freebsd.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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.