From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, qemu-block@nongnu.org, kwolf@redhat.com
Subject: [Qemu-devel] [PATCH v2 00/11] Block layer thread-safety, part 2
Date: Thu, 29 Jun 2017 15:27:38 +0200 [thread overview]
Message-ID: <20170629132749.997-1-pbonzini@redhat.com> (raw)
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)
Paolo Bonzini (11):
qcow2: call CoQueue APIs under CoMutex
coroutine-lock: add qemu_co_rwlock_downgrade and
qemu_co_rwlock_upgrade
vdi: make it thread-safe
vpc: make it thread-safe
vvfat: make it thread-safe
qed: move tail of qed_aio_write_main to qed_aio_write_{cow,alloc}
block: invoke .bdrv_drain callback in coroutine context and from
AioContext
qed: introduce bdrv_qed_init_state
qed: protect table cache with CoMutex
sheepdog: add queue_lock
ssh: support I/O from any AioContext
block/io.c | 42 +++++++--
block/qcow2.c | 4 +-
block/qed-cluster.c | 4 +-
block/qed-l2-cache.c | 6 ++
block/qed-table.c | 24 +++--
block/qed.c | 214 ++++++++++++++++++++++++++++-----------------
block/qed.h | 11 ++-
block/sheepdog.c | 21 ++++-
block/ssh.c | 24 +++--
block/vdi.c | 48 +++++-----
block/vpc.c | 20 ++---
block/vvfat.c | 8 +-
include/block/block_int.h | 2 +-
include/qemu/coroutine.h | 18 ++++
util/qemu-coroutine-lock.c | 35 ++++++++
15 files changed, 331 insertions(+), 150 deletions(-)
--
2.13.0
next reply other threads:[~2017-06-29 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 13:27 Paolo Bonzini [this message]
2017-06-29 13:27 ` [Qemu-devel] [PATCH 01/11] qcow2: call CoQueue APIs under CoMutex Paolo Bonzini
2017-06-29 13:27 ` [Qemu-devel] [PATCH 02/11] coroutine-lock: add qemu_co_rwlock_downgrade and qemu_co_rwlock_upgrade Paolo Bonzini
2017-06-29 13:27 ` [Qemu-devel] [PATCH 03/11] vdi: make it thread-safe Paolo Bonzini
2017-06-29 13:27 ` [Qemu-devel] [PATCH 04/11] vpc: " Paolo Bonzini
2017-07-10 11:32 ` Fam Zheng
2017-06-29 13:27 ` [Qemu-devel] [PATCH 05/11] vvfat: " Paolo Bonzini
2017-06-29 13:27 ` [Qemu-devel] [PATCH 06/11] qed: move tail of qed_aio_write_main to qed_aio_write_{cow, alloc} Paolo Bonzini
2017-06-29 13:27 ` [Qemu-devel] [PATCH 07/11] block: invoke .bdrv_drain callback in coroutine context and from AioContext Paolo Bonzini
2017-06-29 13:27 ` [Qemu-devel] [PATCH 08/11] qed: introduce bdrv_qed_init_state Paolo Bonzini
2017-06-29 15:26 ` Eric Blake
2017-07-17 3:36 ` Fam Zheng
2017-06-29 13:27 ` [Qemu-devel] [PATCH 09/11] qed: protect table cache with CoMutex Paolo Bonzini
2017-06-29 13:27 ` [Qemu-devel] [PATCH 10/11] sheepdog: add queue_lock Paolo Bonzini
2017-06-29 13:27 ` [Qemu-devel] [PATCH 11/11] ssh: support I/O from any AioContext Paolo Bonzini
2017-07-05 21:57 ` [Qemu-devel] [Qemu-block] [PATCH v2 00/11] Block layer thread-safety, part 2 Paolo Bonzini
2017-07-06 23:50 ` [Qemu-devel] " no-reply
2017-07-07 0:05 ` Fam Zheng
2017-07-10 12:18 ` Stefan Hajnoczi
2017-07-10 13:09 ` Fam Zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170629132749.997-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).