[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC v2 0/5] arm AioContext with its own timer stuff
|
From: |
Stefan Hajnoczi |
|
Subject: |
Re: [Qemu-devel] [RFC v2 0/5] arm AioContext with its own timer stuff |
|
Date: |
Mon, 29 Jul 2013 15:36:03 +0200 |
|
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Mon, Jul 29, 2013 at 11:23:52AM +0100, Alex Bligh wrote:
>
>
> --On 29 July 2013 11:22:13 +0200 Stefan Hajnoczi <address@hidden> 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
> >necessary).
>
> 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 your
series - they add the thread safety on top.
Stefan
- Re: [Qemu-devel] [RFC v2 3/5] timer: make qemu_clock_enable sync between disable and timer's cb, (continued)
[Qemu-devel] [RFC v2 4/5] timer: associate three timerlists with AioContext, Liu Ping Fan, 2013/07/28
[Qemu-devel] [RFC v2 5/5] timer: run timers on aio_poll, Liu Ping Fan, 2013/07/28
Re: [Qemu-devel] [RFC v2 0/5] arm AioContext with its own timer stuff, Stefan Hajnoczi, 2013/07/29
Re: [Qemu-devel] [RFC v2 0/5] arm AioContext with its own timer stuff, liu ping fan, 2013/07/29
Re: [Qemu-devel] [RFC v2 0/5] arm AioContext with its own timer stuff, Alex Bligh, 2013/07/29