From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=47212 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PL4ml-0001FU-5x
	for qemu-devel@nongnu.org; Tue, 23 Nov 2010 21:08:40 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1PL4mk-0001rz-15
	for qemu-devel@nongnu.org; Tue, 23 Nov 2010 21:08:39 -0500
Received: from mail-bw0-f45.google.com ([209.85.214.45]:58730)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1PL4mj-0001rt-Qs
	for qemu-devel@nongnu.org; Tue, 23 Nov 2010 21:08:37 -0500
Received: by bwz16 with SMTP id 16so8042559bwz.4
	for <qemu-devel@nongnu.org>; Tue, 23 Nov 2010 18:08:36 -0800 (PST)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <4CEC73A3.7050009@redhat.com>
Date: Wed, 24 Nov 2010 03:08:35 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] qemu-kvm: response to SIGUSR1 to start/stop
	a VCPU (v2)
References: <1290530963-3448-1-git-send-email-aliguori@us.ibm.com>
	<AANLkTin+Bscmmheo1xURNMY_hPxZ+=PgJRveZj_uB44f@mail.gmail.com>
	<4CEC363D.50206@linux.vnet.ibm.com>
	<4CEC5196.8010103@redhat.com> <4CEC671C.1040109@codemonkey.ws>
In-Reply-To: <4CEC671C.1040109@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>, Chris Wright <chrisw@sous-sol.org>, qemu-devel@nongnu.org, kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>

On 11/24/2010 02:15 AM, Anthony Liguori wrote:
>
> Is it signal safe?

Yes, at heart it is just a somewhat more expensive access to 
pthread_self()->some_array[key].

> BTW, this is all only theoretical.  This is in the KVM io thread code
> which is already highly unportable.

True, and newer versions of GCC emulate __thread even on Windows.

Paolo