qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	patches@linaro.org,
	"Dr. David Alan Gilbert" <david.gilbert@linaro.org>,
	qemu-devel@nongnu.org, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/3] Make cpu_single_env thread-local
Date: Thu, 27 Oct 2011 17:12:04 +0200	[thread overview]
Message-ID: <4EA974C4.9010004@redhat.com> (raw)
In-Reply-To: <4EA9747B.7010703@suse.de>

On 10/27/2011 05:10 PM, Andreas Färber wrote:
> Am 27.10.2011 13:37, schrieb Peter Maydell:
>> From: Paolo Bonzini<pbonzini@redhat.com>
>>
>> Make cpu_single_env thread-local. This fixes a regression
>> in handling of multi-threaded programs in linux-user mode
>> (bug 823902).
>>
>> Signed-off-by: Paolo Bonzini<pbonzini@redhat.com>
>> [Peter Maydell: rename tls_cpu_single_env to cpu_single_env]
>> Signed-off-by: Peter Maydell<peter.maydell@linaro.org>
>> ---
>>   cpu-all.h |    4 +++-
>>   exec.c    |    2 +-
>>   2 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/cpu-all.h b/cpu-all.h
>> index 42a5fa0..5f47ab8 100644
>> --- a/cpu-all.h
>> +++ b/cpu-all.h
>> @@ -20,6 +20,7 @@
>>   #define CPU_ALL_H
>>
>>   #include "qemu-common.h"
>> +#include "qemu-tls.h"
>>   #include "cpu-common.h"
>>
>>   /* some important defines:
> [8<]
>
> Is there a reason not to include this from qemu-common.h? To avoid
> accidental use in unsuited cases? If so, add an explicit comment to
> either qemu-common.h or Jan's comment in qemu-tls.h to avoid someone
> doing such a cleanup/simplification patch?

I think we're evolving towards having qemu-common.h as a common place 
for system header inclusions, but not really for QEMU-specific headers.

Paolo

  reply	other threads:[~2011-10-27 15:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 11:37 [Qemu-devel] [PATCH v2 0/3] TLS abstraction layer for thread-local cpu_single_env on Linux Peter Maydell
2011-10-27 11:37 ` [Qemu-devel] [PATCH v2 1/3] qemu-tls.h: Add abstraction layer for TLS variables Peter Maydell
2011-10-27 15:04   ` Andreas Färber
2011-10-27 15:08     ` Paolo Bonzini
2011-10-27 15:15     ` Peter Maydell
2011-10-27 15:18       ` Paolo Bonzini
2011-10-27 16:18     ` Andreas Färber
2011-10-28  7:27     ` Markus Armbruster
2011-10-28  7:45       ` Peter Maydell
2011-10-27 11:37 ` [Qemu-devel] [PATCH v2 2/3] darwin-user/main.c: Drop unused cpu_single_env definition Peter Maydell
2011-10-27 13:22   ` Andreas Färber
2011-10-27 11:37 ` [Qemu-devel] [PATCH v2 3/3] Make cpu_single_env thread-local Peter Maydell
2011-10-27 15:10   ` Andreas Färber
2011-10-27 15:12     ` Paolo Bonzini [this message]
2011-10-27 16:20     ` Andreas Färber

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=4EA974C4.9010004@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=david.gilbert@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --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).