> On 11/29/2009 05:38 PM, Andreas Färber wrote:
>> Am 29.11.2009 um 16:29 schrieb Avi Kivity:
>>> Where is __thread not supported?
>> Apple, Sun.
Some flavours of uClinux :-)
Avi Kivity wrote:
> Well, pthread_getspecific is around 130 bytes of code, whereas __thread
> is just on instruction. Ma
Am 29.11.2009 um 16:42 schrieb Avi Kivity:
On 11/29/2009 05: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 associ
On 11/29/2009 05: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 th
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
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
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.
Signed-
