qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Dr. David Alan Gilbert" <david.gilbert@linaro.org>,
	Jan Kiszka <jan.kiszka@siemens.com>
Subject: [Qemu-devel] [PATCH 0/2] TLS abstraction layer for thread-local cpu_single_env on Linux
Date: Wed, 26 Oct 2011 17:07:09 +0100	[thread overview]
Message-ID: <1319645231-14151-1-git-send-email-peter.maydell@linaro.org> (raw)

These patches add enough of the TLS abstraction layer to allow us
to make cpu_single_env thread-local on Linux systems. This fixes
the regression described in bug 823902 for the 1.0 release; we
can add the Win32 and POSIX implementations later.          

I haven't included Paolo's "Prepare Windows port for thread-local
cpu_single_env" patch -- it would be safe to do so but it isn't
necessary until we actually implement TLS for Win32.     

Paolo Bonzini (1):
  Make cpu_single_env thread-local

Peter Maydell (1):
  qemu-tls.h: Add abstraction layer for TLS variables

 cpu-all.h          |    4 +++-
 darwin-user/main.c |    2 --
 exec.c             |    2 +-
 qemu-tls.h         |   51 +++++++++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 55 insertions(+), 4 deletions(-)
 create mode 100644 qemu-tls.h

             reply	other threads:[~2011-10-26 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 16:07 Peter Maydell [this message]
2011-10-26 16:07 ` [Qemu-devel] [PATCH 1/2] qemu-tls.h: Add abstraction layer for TLS variables Peter Maydell
2011-10-26 17:08   ` Paolo Bonzini
2011-10-26 17:38     ` Peter Maydell
2011-10-26 16:07 ` [Qemu-devel] [PATCH 2/2] Make cpu_single_env thread-local Peter Maydell
2011-10-26 16:20   ` Andreas Färber
2011-10-26 16:58     ` Peter Maydell

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=1319645231-14151-1-git-send-email-peter.maydell@linaro.org \
    --to=peter.maydell@linaro.org \
    --cc=david.gilbert@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=pbonzini@redhat.com \
    --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).