From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial@nongnu.org, Ed Maste <emaste@freebsd.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tls.h: Enable TLS on FreeBSD
Date: Tue, 25 Jun 2013 12:58:12 +0200 [thread overview]
Message-ID: <51C977C4.5010603@redhat.com> (raw)
In-Reply-To: <CAFEAcA-oOr_twUKhOg3j21dmpOkNpMZ-4KYmnxH=W6Qfi1X0vw@mail.gmail.com>
Il 25/06/2013 12:56, Peter Maydell ha scritto:
> On 24 June 2013 22:15, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> I and Stefan Hajnoczi have almost the same idea implemented in QEMU
>> (except that get_foo() returns a pointer to the variable). But
>> pthread_get/setspecific would be too slow for cpu_single_env, so we're
>> just switching to __thread for cpu_single_env (for Linux in our patches,
>> but you can add FreeBSD too once it's needed).
>
> By the way, what's the plan for Windows? Does that support
> __thread too, or will there still need to be some windows
> specific magic?
__thread is supported but slow, so there is a small amount of
Windows-specific magic (but it won't affect the users of tls.h).
Paolo
next prev parent reply other threads:[~2013-06-25 10:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 19:21 [Qemu-devel] [PATCH] tls.h: Enable TLS on FreeBSD Ed Maste
2013-06-24 21:15 ` Paolo Bonzini
2013-06-24 21:30 ` Peter Maydell
2013-06-25 6:18 ` Paolo Bonzini
2013-06-25 10:56 ` Peter Maydell
2013-06-25 10:58 ` Paolo Bonzini [this message]
2013-06-28 10:34 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2013-06-28 12:54 ` Ed Maste
2013-06-28 13:03 ` Paolo Bonzini
2013-06-28 13:05 ` Peter Maydell
2013-06-28 14:08 ` Ed Maste
2013-06-28 14:47 ` Paolo Bonzini
2013-06-28 14:55 ` Peter Maydell
2013-06-28 15:11 ` Paolo Bonzini
2013-06-28 15:35 ` Ed Maste
2013-06-28 15:37 ` Paolo Bonzini
2013-07-01 8:03 ` 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=51C977C4.5010603@redhat.com \
--to=pbonzini@redhat.com \
--cc=emaste@freebsd.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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 NNTP newsgroup(s).