From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Ed Maste <emaste@freebsd.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-thread: add TLS wrappers
Date: Mon, 1 Jul 2013 14:34:53 +0200 [thread overview]
Message-ID: <20130701123453.GA19303@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAFEAcA-tJHW7LUD6_mwF=UKVgLUUo=Oyt_hf+Xjm8JoQxauEHg@mail.gmail.com>
On Mon, Jul 01, 2013 at 10:54:56AM +0100, Peter Maydell wrote:
> On 1 July 2013 10:35, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > From: Paolo Bonzini <pbonzini@redhat.com>
> >
> > Fast TLS is not available on some platforms, but it is always nice to
> > use it. This wrapper implementation falls back to pthread_get/setspecific
> > on POSIX systems that lack __thread, but uses the dynamic linker's TLS
> > support on Linux and Windows.
> >
> > The user shall call tls_alloc_foo() in every thread that needs to access
> > the variable---exactly once and before any access. foo is the name of
> > the variable as passed to DECLARE_TLS and DEFINE_TLS. Then,
> > tls_get_foo() will return the address of the variable. It is guaranteed
> > to remain the same across the lifetime of a thread, so you can cache it.
>
> > ##########################################
> > +# check for TLS runtime
> > +
> > +# Some versions of mingw include the "magic" definitions that make
> > +# TLS work, some don't. Check for it.
> > +
> > +if test "$mingw32" = yes; then
> > + cat > $TMPC << EOF
> > +int main(void) {}
>
> Execution falls off the end of function without returning a value
> (I would expect the compiler to issue a warning about this.)
You are right, gcc emits a warning.
> > +#ifndef QEMU_TLS_H
> > +#define QEMU_TLS_H
> > +
> > +#if defined __linux__
> > +#define DECLARE_TLS(type, x) \
> > +extern __thread typeof(type) x; \
> > + \
> > +static inline typeof(type) *tls_get_##x(void) \
> > +{ \
> > + return &x; \
> > +} \
> > + \
> > +static inline typeof(type) *tls_alloc_##x(void) \
> > +{ \
> > + return &x; \
> > +} \
> > + \
> > +extern int dummy_##__LINE__
>
> What's this for?
It makes the DECLARE_TLS() macro use a semicolon.
next prev parent reply other threads:[~2013-07-01 12:35 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 [this message]
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
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=20130701123453.GA19303@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=emaste@freebsd.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).