From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NF4ZI-0005Q6-S4 for qemu-devel@nongnu.org; Mon, 30 Nov 2009 06:37:24 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NF4ZD-0005OE-U8 for qemu-devel@nongnu.org; Mon, 30 Nov 2009 06:37:24 -0500 Received: from [199.232.76.173] (port=33898 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NF4ZD-0005O7-IU for qemu-devel@nongnu.org; Mon, 30 Nov 2009 06:37:19 -0500 Received: from lo.gmane.org ([80.91.229.12]:58205) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NF4ZD-0002RD-CO for qemu-devel@nongnu.org; Mon, 30 Nov 2009 06:37:19 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NF4ZA-0002AB-65 for qemu-devel@nongnu.org; Mon, 30 Nov 2009 12:37:16 +0100 Received: from 93-34-210-248.ip51.fastwebnet.it ([93.34.210.248]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Nov 2009 12:37:16 +0100 Received: from pbonzini by 93-34-210-248.ip51.fastwebnet.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Nov 2009 12:37:16 +0100 From: Paolo Bonzini Date: Mon, 30 Nov 2009 12:36:53 +0100 Message-ID: References: <1259256300-23937-1-git-send-email-glommer@redhat.com> <1259256300-23937-2-git-send-email-glommer@redhat.com> <1259256300-23937-3-git-send-email-glommer@redhat.com> <4B129372.1070204@redhat.com> <5E6C2888-0B2C-4BBE-A0E6-B9ECAB50F5F0@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit In-Reply-To: <5E6C2888-0B2C-4BBE-A0E6-B9ECAB50F5F0@web.de> Sender: news Subject: [Qemu-devel] Re: [PATCH 2/7] store thread-specific env information List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 11/29/2009 04:38 PM, Andreas Färber wrote: > > Am 29.11.2009 um 16:29 schrieb Avi Kivity: > >> On 11/26/2009 07:24 PM, Glauber Costa wrote: >>> Since we'll have multiple cpu threads, at least for kvm, we need a >>> way to store >>> and retrieve the CPUState associated with the current execution thread. >>> For the I/O thread, this will be NULL. >>> >>> I am using pthread functions for that, for portability, but we could >>> as well >>> use __thread keyword. >>> >>> >> >> Where is __thread not supported? > > Apple, Sun. Not sure about Sun. Anyway on Windows neither __thread nor pthread_getspecific is supported, so some configury is needed anyway. Paolo