On Thu, 06/29 15:27, Paolo Bonzini wrote: > This part takes care of drivers and devices, making sure that they can > accept concurrent I/O from multiple AioContext. > > The following drivers are thread-safe without using any QemuMutex/CoMutex: > crypto, gluster, null, rbd, win32-aio. NBD has already been fixed, > because the patch fixed an unrelated testcase. > > The following drivers already use mutexes for everything except possibly > snapshots, which do not (yet?) need protection: bochs, cloop, dmg, qcow, > parallels, vhdx, vmdk, curl, iscsi, nfs. > > The following drivers already use mutexes for _almost_ everything: vpc > (missing get_block_status), vdi (missing bitmap access), vvfat (missing > commit), not protected), qcow2 (must call CoQueue APIs under CoMutex). > They are fixed by patches 1-5. > > The following drivers must be changed to use CoMutex to protect internal > data: qed (patches 6-9), sheepdog (patch 10). > > The following driver must be changed to support I/O from any AioContext: > ssh. It is fixed by patch 11. > > Paolo > > v1->v2: new patch 8 + adjustments to patch 9 to fix qemu-iotests testcase > 183 (bdrv_invalidate_cache from block migration)
Thanks, queued: https://github.com/famz/qemu/tree/staging Fam
