Il 29/07/2013 05:16, Liu Ping Fan ha scritto:
Currently, timers run on iothread inside QBL, this limits the usage
of timers in some case, e.g. virtio-blk-dataplane. In order to run
timers on private thread based on different clocksource, we arm each
AioContext with three timer lists in
On Mon, Jul 29, 2013 at 2:32 PM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 29/07/2013 05:16, Liu Ping Fan ha scritto:
Currently, timers run on iothread inside QBL, this limits the usage
of timers in some case, e.g. virtio-blk-dataplane. In order to run
timers on private thread based on
Il 29/07/2013 10:20, liu ping fan ha scritto:
Another issue is that deadline computation is not using the AioContext's
timer lists.
Sorry, can not catch the meaning. When AioContext has its own timer
lists, it will have its own deadline(for ppoll timeout). So the
computation should be
On Mon, Jul 29, 2013 at 9:11 PM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 29/07/2013 10:20, liu ping fan ha scritto:
Another issue is that deadline computation is not using the AioContext's
timer lists.
Sorry, can not catch the meaning. When AioContext has its own timer
lists, it will
Currently, timers run on iothread inside QBL, this limits the usage
of timers in some case, e.g. virtio-blk-dataplane. In order to run
timers on private thread based on different clocksource, we arm each
AioContext with three timer lists in according to three clocksource
(QemuClock).
A little
