[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC v2 4/5] timer: associate three timerlists with Aio
|
From: |
Paolo Bonzini |
|
Subject: |
Re: [Qemu-devel] [RFC v2 4/5] timer: associate three timerlists with AioContext |
|
Date: |
Mon, 29 Jul 2013 15:11:57 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 |
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 based on AioContext's timer lists, right?
Associating the main loop's timer lists to other AioContexts is really
really wrong... It is _already_ wrong to run timers in the main
AioContext's aio_poll (because timers may not be ready to run from an
arbitrary aio_poll), it is even worse to run them in other threads
without taking the BQL.
What exactly is the purpose of this series?
Paolo
- Re: [Qemu-devel] [RFC v2 1/5] timer: protect timers_state with lock, (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