On 09/09/2015 13:01, Juan Quintela wrote:
> Paolo Bonzini wrote:
>> On 09/09/2015 12:41, Juan Quintela wrote:
> +qemu_mutex_unlock_iothread();
> +atomic_set(&cpu->throttle_thread_scheduled, 0);
> +g_usleep(sleeptime_ns / 1000); /* Convert ns to us for usleep call */
>
Paolo Bonzini wrote:
> On 09/09/2015 12:41, Juan Quintela wrote:
>>> > +qemu_mutex_unlock_iothread();
>>> > +atomic_set(&cpu->throttle_thread_scheduled, 0);
>>> > +g_usleep(sleeptime_ns / 1000); /* Convert ns to us for usleep call */
>>> > +qemu_mutex_lock_iothread();
>>
>> Why is
Paolo Bonzini wrote:
> On 08/09/2015 19:12, Jason J. Herne wrote:
>> Provide a method to throttle guest cpu execution. CPUState is augmented with
>> timeout controls and throttle start/stop functions. To throttle the guest cpu
>> the caller simply has to call the throttle set function and provide
On 09/09/2015 12:41, Juan Quintela wrote:
>> > +qemu_mutex_unlock_iothread();
>> > +atomic_set(&cpu->throttle_thread_scheduled, 0);
>> > +g_usleep(sleeptime_ns / 1000); /* Convert ns to us for usleep call */
>> > +qemu_mutex_lock_iothread();
>
> Why is this thread safe?
>
> qemu
"Jason J. Herne" wrote:
> Provide a method to throttle guest cpu execution. CPUState is augmented with
> timeout controls and throttle start/stop functions. To throttle the guest cpu
> the caller simply has to call the throttle set function and provide a
> percentage
> of throttle time.
>
> Signe
On 08/09/2015 19:12, Jason J. Herne wrote:
> Provide a method to throttle guest cpu execution. CPUState is augmented with
> timeout controls and throttle start/stop functions. To throttle the guest cpu
> the caller simply has to call the throttle set function and provide a
> percentage
> of thro
Provide a method to throttle guest cpu execution. CPUState is augmented with
timeout controls and throttle start/stop functions. To throttle the guest cpu
the caller simply has to call the throttle set function and provide a percentage
of throttle time.
Signed-off-by: Jason J. Herne
Reviewed-by:
