Il 10/08/2013 05:27, liu ping fan ha scritto: >> > ... except if we get rid of TimerListGroup completely and put it in >> > AioContext. To do so, we can have _two_ AioContexts in main-loop.c. >> > One is for the block layer, the other is only used for timers. Later we > Why can the AioContexts of block layer NOT hold timers? For the > reason mainloop's iohandler runs after it? Or any reason raised by > blocklayer itself?
The point of this series is to make the AioContexts of the block layer able to hold timers. At the same time, however, the main loop's timers cannot run during a qemu_aio_wait(), as that would be backwards-incompatible. So I'm proposing to have two AioContext, and in the future separate timers-for-the-block-layer from timers-for-everything-else. Paolo
