On Wed, Sep 18, 2013 at 11:25:25AM +0200, Paolo Bonzini wrote: > Il 18/09/2013 11:02, Alex Bligh ha scritto: > > Paolo, > > > > On 18 Sep 2013, at 09:23, Alex Bligh wrote: > > > >>> Yes, that was my understanding too. Can we do it for 1.7? > > > > Whilst we are changing the calling semantics, do you think > > qemu_coroutine_yield() should also run the timers for the > > aio_context? IE should timers always be deferred to the > > next qemu_aio_wait() / aio_poll(), or should we make it > > so they can run whenever there is a 'schedule' between > > coroutines? > > No, they should be left for the next aio_poll().
I agree. Besides the side-effects, I want to avoid coupling coroutines too deeply with event loop entities like timers. They should not know about each other. Stefan
