From: Paolo Bonzini <pbonzini@redhat.com>
To: David Gilbert <david.gilbert@linaro.org>
Cc: peter.maydell@linaro.org, patches@linaro.org,
Jan Kiszka <jan.kiszka@web.de>,
agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Make cpu_single_env thread local (Linux only for now)
Date: Sat, 08 Oct 2011 15:41:58 +0200 [thread overview]
Message-ID: <4E905326.1070908@redhat.com> (raw)
In-Reply-To: <CA+1XiScKELM2L5hXJnNsF0XabFKw6NY4Ce1LAZj_cb2VFfxcSA@mail.gmail.com>
On 10/07/2011 07:29 PM, David Gilbert wrote:
> Hmm this got a bit more complex than the original patch; still it covers a lot
> more bases.
>
> Should this also replace the THREAD that's defined in
> linux-user/qemu.h and bsd-user/qemu.h (that is __thread if built with
> NPTL)?
> It seems to only be there for 'thread_env' which is also a CPUState*
> (hmm - what state does that contain that cpu_single_env doesn't?)
Yes, I wouldn't be surprised if thread_env can just go. That would be a
separate cleanup, however.
Paolo
next prev parent reply other threads:[~2011-10-08 13:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 16:33 [Qemu-devel] [PATCH] Make cpu_single_env thread local (Linux only for now) Dr. David Alan Gilbert
2011-10-03 17:51 ` Jan Kiszka
2011-10-04 15:10 ` Lluís Vilanova
2011-10-04 17:26 ` Jan Kiszka
2011-10-05 7:08 ` Paolo Bonzini
2011-10-05 7:52 ` Jan Kiszka
2011-10-05 9:21 ` Paolo Bonzini
2011-10-07 17:29 ` David Gilbert
2011-10-08 13:41 ` Paolo Bonzini [this message]
2011-10-26 14:03 ` Peter Maydell
2011-10-26 14:39 ` Paolo Bonzini
2011-10-26 14:54 ` Peter Maydell
2011-10-26 14:59 ` Paolo Bonzini
2011-10-26 15:02 ` Jan Kiszka
2011-10-26 15:09 ` Peter Maydell
2011-10-26 15:13 ` Jan Kiszka
2011-10-26 15:18 ` Peter Maydell
2011-10-26 16:02 ` Jan Kiszka
2011-10-26 16:27 ` Andreas Färber
2011-10-26 16:31 ` Jan Kiszka
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=4E905326.1070908@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=david.gilbert@linaro.org \
--cc=jan.kiszka@web.de \
--cc=patches@linaro.org \
--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).