Sergey Fedorov writes:
> On 27/05/16 18:25, Paolo Bonzini wrote:
>>
>> On 27/05/2016 17:07, Sergey Fedorov wrote:
>>> 1. Make 'cpu->thread_kicked' access atomic
>>> 2. Remove global 'exit_request' and use per-CPU 'exit_request'
>>> 3. Change how 'current_cpu' is set
>>> 4. Re
On 27/05/16 18:25, Paolo Bonzini wrote:
>
> On 27/05/2016 17:07, Sergey Fedorov wrote:
>> 1. Make 'cpu->thread_kicked' access atomic
>> 2. Remove global 'exit_request' and use per-CPU 'exit_request'
>> 3. Change how 'current_cpu' is set
>> 4. Reorganize round-robin CPU TCG threa
On 27/05/16 17:55, Paolo Bonzini wrote:
>
> On 27/05/2016 15:57, Sergey Fedorov wrote:
>> 1. Make 'cpu->thread_kicked' access atomic
>> 2. Remove global 'exit_request' and use per-CPU 'exit_request'
>> 3. Change how 'current_cpu' is set
>> 4. Reorganize round-robin CPU TCG thread function
>> 5
On 27/05/2016 17:07, Sergey Fedorov wrote:
>>> >> 1. Make 'cpu->thread_kicked' access atomic
>>> >> 2. Remove global 'exit_request' and use per-CPU 'exit_request'
>>> >> 3. Change how 'current_cpu' is set
>>> >> 4. Reorganize round-robin CPU TCG thread function
>>> >> 5. Enable 'mmap_lock' f
On 27/05/2016 15:57, Sergey Fedorov wrote:
> 1. Make 'cpu->thread_kicked' access atomic
> 2. Remove global 'exit_request' and use per-CPU 'exit_request'
> 3. Change how 'current_cpu' is set
> 4. Reorganize round-robin CPU TCG thread function
> 5. Enable 'mmap_lock' for system mode emulation
On 05/04/16 18:32, Alex Bennée wrote:
> From: KONRAD Frederic
>
> This allows the user to switch on multi-thread behaviour and spawn a
> thread per-vCPU. For a simple test like:
>
> ./arm/run ./arm/locking-test.flat -smp 4 -tcg mttcg=on
>
> Will now use 4 vCPU threads and have an expected FAIL (
From: KONRAD Frederic
This allows the user to switch on multi-thread behaviour and spawn a
thread per-vCPU. For a simple test like:
./arm/run ./arm/locking-test.flat -smp 4 -tcg mttcg=on
Will now use 4 vCPU threads and have an expected FAIL (instead of the
unexpected PASS) as the default mode
