From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NEluy-00041i-Fj
	for qemu-devel@nongnu.org; Sun, 29 Nov 2009 10:42:32 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NEluu-000410-VG
	for qemu-devel@nongnu.org; Sun, 29 Nov 2009 10:42:32 -0500
Received: from [199.232.76.173] (port=39423 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NEluu-00040x-QS
	for qemu-devel@nongnu.org; Sun, 29 Nov 2009 10:42:28 -0500
Received: from mx1.redhat.com ([209.132.183.28]:9630)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1NEluu-0002Em-Ee
	for qemu-devel@nongnu.org; Sun, 29 Nov 2009 10:42:28 -0500
Message-ID: <4B129661.1000808@redhat.com>
Date: Sun, 29 Nov 2009 17:42:25 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 2/7] store thread-specific env information
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>
In-Reply-To: <5E6C2888-0B2C-4BBE-A0E6-B9ECAB50F5F0@web.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
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.gnu.org/pipermail/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: =?ISO-8859-1?Q?Andreas_F=E4rber?= <andreas.faerber@web.de>
Cc: Glauber Costa <glommer@redhat.com>, aliguori@us.ibm.com, qemu-devel@nongnu.org

On 11/29/2009 05:38 PM, Andreas F=E4rber 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=20
>>> way to store
>>> and retrieve the CPUState associated with the current execution threa=
d.
>>> For the I/O thread, this will be NULL.
>>>
>>> I am using pthread functions for that, for portability, but we could=20
>>> as well
>>> use __thread keyword.
>>>
>>>
>>
>> Where is __thread not supported?
>
> Apple, Sun.

Well, pthread_getspecific is around 130 bytes of code, whereas __thread=20
is just on instruction.  Maybe we should support both.

--=20
error compiling committee.c: too many arguments to function