All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Dr. David Alan Gilbert" <david.gilbert@linaro.org>,
	patches@linaro.org, "Jan Kiszka" <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] TLS abstraction layer for thread-local cpu_single_env on Linux
Date: Mon, 31 Oct 2011 13:08:39 -0500	[thread overview]
Message-ID: <4EAEE427.8010700@us.ibm.com> (raw)
In-Reply-To: <CAFEAcA_LS1zC8_o_bQ+X4sz8+6TUPvUus0D9-7y1ARw=ws9PyQ@mail.gmail.com>

On 10/31/2011 08:40 AM, Peter Maydell wrote:
> An early ping since I have no idea who counts as the submaintainer
> for this patchset and it definitely needs to go in for 1.0...

I'm in the process of testing them and will apply provided nothing breaks.

Regards,

Anthony Liguori

>
> thanks
> -- PMM
>
> On 28 October 2011 10:52, Peter Maydell<peter.maydell@linaro.org>  wrote:
>> 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.
>>
>> Changes v1->v2:
>>   * fix Paolo's email address
>>   * split the darwin-user change out into a separate patch
>>   * drop the 'tls_' prefix from the cpu_single_env tls var name
>> Changes v2->v3:
>>   * minor rearrangement of copyright notice in comment
>>   * added a missing Signed-off-by
>>   * fixed the name of the multiple-include-guard #define
>>
>> Paolo Bonzini (2):
>>   darwin-user/main.c: Drop unused cpu_single_env definition
>>   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         |   52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>   4 files changed, 56 insertions(+), 4 deletions(-)
>>   create mode 100644 qemu-tls.h
>
>

  parent reply	other threads:[~2011-10-31 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28  9:52 [Qemu-devel] [PATCH v3 0/3] TLS abstraction layer for thread-local cpu_single_env on Linux Peter Maydell
2011-10-28  9:52 ` [Qemu-devel] [PATCH v3 1/3] qemu-tls.h: Add abstraction layer for TLS variables Peter Maydell
2011-10-28  9:52 ` [Qemu-devel] [PATCH v3 2/3] darwin-user/main.c: Drop unused cpu_single_env definition Peter Maydell
2011-10-28  9:52 ` [Qemu-devel] [PATCH v3 3/3] Make cpu_single_env thread-local Peter Maydell
2011-10-31 13:40 ` [Qemu-devel] [PATCH v3 0/3] TLS abstraction layer for thread-local cpu_single_env on Linux Peter Maydell
2011-10-31 17:28   ` Jan Kiszka
2011-10-31 18:08   ` Anthony Liguori [this message]
2011-11-01 16:20 ` Anthony Liguori

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=4EAEE427.8010700@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=david.gilbert@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=patches@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.