Re: [Qemu-block] [PATCH v2] virtio-blk: schedule virtio_notify_config to run on main context

2019-09-16 Thread Kevin Wolf
Am 13.09.2019 um 12:56 hat Sergio Lopez geschrieben: > virtio_notify_config() needs to acquire the global mutex, which isn't > allowed from an iothread, and may lead to a deadlock like this: > > - main thead > * Has acquired: qemu_global_mutex. > * Is trying the acquire: iothread AioContext

Re: [Qemu-block] [PATCH v2] virtio-blk: schedule virtio_notify_config to run on main context

2019-09-13 Thread John Snow
On 9/13/19 6:56 AM, Sergio Lopez wrote: > virtio_notify_config() needs to acquire the global mutex, which isn't > allowed from an iothread, and may lead to a deadlock like this: > > - main thead > * Has acquired: qemu_global_mutex. > * Is trying the acquire: iothread AioContext lock via >

[Qemu-block] [PATCH v2] virtio-blk: schedule virtio_notify_config to run on main context

2019-09-13 Thread Sergio Lopez
virtio_notify_config() needs to acquire the global mutex, which isn't allowed from an iothread, and may lead to a deadlock like this: - main thead * Has acquired: qemu_global_mutex. * Is trying the acquire: iothread AioContext lock via AIO_WAIT_WHILE (after aio_poll). - iothread *