[Qemu-devel] [PATCH 2/9] main-loop: introduce qemu_mutex_iothread_locked

2015-07-02 Thread Paolo Bonzini
This function will be used to avoid recursive locking of the iothread lock whenever address_space_rw/ld*/st* are called with the BQL held, which is almost always the case. Tracking whether the iothread is owned is very cheap (just use a TLS variable) but requires some care because now the lock

[Qemu-devel] [PATCH 2/9] main-loop: introduce qemu_mutex_iothread_locked

2015-06-24 Thread Paolo Bonzini
This function will be used to avoid recursive locking of the iothread lock whenever address_space_rw/ld*/st* are called with the BQL held, which is almost always the case. Tracking whether the iothread is owned is very cheap (just use a TLS variable) but requires some care because now the lock

Re: [Qemu-devel] [PATCH 2/9] main-loop: introduce qemu_mutex_iothread_locked

2015-06-23 Thread Fam Zheng
On Thu, 06/18 18:47, Paolo Bonzini wrote: This function will be used to avoid recursive locking of the iothread lock whenever address_space_rw/ld*/st* are called with the BQL held, which is almost always the case. Tracking whether the iothread is owned is very cheap (just use a TLS

[Qemu-devel] [PATCH 2/9] main-loop: introduce qemu_mutex_iothread_locked

2015-06-18 Thread Paolo Bonzini
This function will be used to avoid recursive locking of the iothread lock whenever address_space_rw/ld*/st* are called with the BQL held, which is almost always the case. Tracking whether the iothread is owned is very cheap (just use a TLS variable) but requires some care because now the lock