On Mon, Jul 29, 2013 at 5:22 PM, Stefan Hajnoczi wrote:
> On Mon, Jul 29, 2013 at 11:16:03AM +0800, Liu Ping Fan wrote:
>> summary of the model:
>> Three qemu-wide clock source allowed in system. And each AioContext has
>> three corresponding timer list to run timer against clocksource.
>>
>> rf
--On 29 July 2013 15:36:03 +0200 Stefan Hajnoczi
wrote:
I should say PingFan has probably paid more attention to thread safety
than me, as my work was intended to be applied before AioContexts were
used by multiple threads.
Exactly. That's why I think these patches should be based on you
On Mon, Jul 29, 2013 at 11:23:52AM +0100, Alex Bligh wrote:
>
>
> --On 29 July 2013 11:22:13 +0200 Stefan Hajnoczi wrote:
>
> >The potential for overlap with Alex Bligh's series is large. Can you
> >base your patches on his v4?
> >
> >It seems the difference is that you make clock sources to b
--On 29 July 2013 11:22:13 +0200 Stefan Hajnoczi wrote:
The potential for overlap with Alex Bligh's series is large. Can you
base your patches on his v4?
It seems the difference is that you make clock sources to be available
globally while Alex's series uses rt_clock (no synchronization
nec
--On 29 July 2013 11:16:03 +0800 Liu Ping Fan wrote:
summary of the model:
Three qemu-wide clock source allowed in system. And each AioContext has
three corresponding timer list to run timer against clocksource.
rfcv2:
drop patches about alarm-timer(if timeout of poll will not satisfy,
On Mon, Jul 29, 2013 at 11:16:03AM +0800, Liu Ping Fan wrote:
> summary of the model:
> Three qemu-wide clock source allowed in system. And each AioContext has
> three corresponding timer list to run timer against clocksource.
>
> rfcv2:
>drop patches about alarm-timer(if timeout of poll wil
summary of the model:
Three qemu-wide clock source allowed in system. And each AioContext has
three corresponding timer list to run timer against clocksource.
rfcv2:
drop patches about alarm-timer(if timeout of poll will not satisfy, will
come back to it)
fix qemu_clock_enable sync proble
