Re: [Qemu-devel] [PATCH 01/18] iothread: release iothread around aio_poll

2015-09-28 Thread Paolo Bonzini
On 28/09/2015 11:50, Stefan Hajnoczi wrote: > On Thu, Aug 06, 2015 at 03:35:59PM +0200, Paolo Bonzini wrote: >> This is the first step towards having fine-grained critical sections in >> dataplane threads, which resolves lock ordering problems between >> address_space_* functions (which need the

Re: [Qemu-devel] [PATCH 01/18] iothread: release iothread around aio_poll

2015-09-28 Thread Stefan Hajnoczi
On Thu, Aug 06, 2015 at 03:35:59PM +0200, Paolo Bonzini wrote: > This is the first step towards having fine-grained critical sections in > dataplane threads, which resolves lock ordering problems between > address_space_* functions (which need the BQL when doing MMIO, even > after we complete RCU-b

Re: [Qemu-devel] [PATCH 01/18] iothread: release iothread around aio_poll

2015-09-09 Thread Paolo Bonzini
On 09/09/2015 08:06, Fam Zheng wrote: > This patch will probably go in before aio_disable_clients, Actually I think it's blocked by aio_disable_clients. > if any, but I'm not > quite confident about the interface yet: listing a precise set of clients from > monitor is an ugly coupling between m

Re: [Qemu-devel] [PATCH 01/18] iothread: release iothread around aio_poll

2015-09-08 Thread Fam Zheng
On Thu, 08/06 15:35, Paolo Bonzini wrote: > This is the first step towards having fine-grained critical sections in > dataplane threads, which resolves lock ordering problems between > address_space_* functions (which need the BQL when doing MMIO, even > after we complete RCU-based dispatch) and th

[Qemu-devel] [PATCH 01/18] iothread: release iothread around aio_poll

2015-08-06 Thread Paolo Bonzini
This is the first step towards having fine-grained critical sections in dataplane threads, which resolves lock ordering problems between address_space_* functions (which need the BQL when doing MMIO, even after we complete RCU-based dispatch) and the AioContext. Because AioContext does not use con