From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, qemu-block@nongnu.org, stefanha@redhat.com
Subject: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part
Date: Thu, 6 Jul 2017 18:38:17 +0200 [thread overview]
Message-ID: <20170706163828.24082-1-pbonzini@redhat.com> (raw)
Here, patches 1-6 make the remaining part of the block layer thread safe.
Patches 7-11 start removing aio_context_acquire/release, so the line
count goes down instead of up.
This is the penultimate series. The remaining part makes virtio-blk,
virtio-scsi and block jobs thread safe, so that the AioContext lock
can go away altogether.
Paolo
Paolo Bonzini (11):
block: prepare write threshold code for thread safety
block: make write-threshold thread-safe
util: use RCU accessors for notifiers
block: make before-write notifiers thread-safe
block-backup: add reqs_lock
block: more notes on locking
block: do not acquire AioContext in check_to_replace_node
block: drain I/O around key management
block/replication: do not acquire AioContext
block: do not take AioContext around reopen
block/snapshot: do not take AioContext lock
qdev: do not take AioContext when releasing (and thus closing)
backends
block.c | 19 +++--------
block/backup.c | 37 +++++++++++++++------
block/block-backend.c | 5 ---
block/commit.c | 2 +-
block/io.c | 12 +++++++
block/mirror.c | 9 ------
block/replication.c | 56 ++++++++------------------------
block/snapshot.c | 28 +---------------
block/write-threshold.c | 39 +++++++++++-----------
blockdev.c | 70 ++++++++++++----------------------------
hmp.c | 7 ----
include/block/block.h | 2 +-
include/block/block_backup.h | 2 +-
include/block/block_int.h | 31 ++++++++++++++++--
include/block/snapshot.h | 4 +--
migration/savevm.c | 22 -------------
monitor.c | 10 ++----
qemu-io-cmds.c | 2 +-
util/notify.c | 13 ++++----
19 files changed, 142 insertions(+), 228 deletions(-)
--
2.13.0
next reply other threads:[~2017-07-06 16:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 16:38 Paolo Bonzini [this message]
2017-07-06 16:38 ` [Qemu-devel] [PATCH 01/11] block: prepare write threshold code for thread safety Paolo Bonzini
2017-07-06 16:51 ` Eric Blake
2017-07-10 13:21 ` Stefan Hajnoczi
2017-07-10 16:16 ` Paolo Bonzini
2017-07-10 16:22 ` Eric Blake
2017-07-06 16:38 ` [Qemu-devel] [PATCH 02/11] block: make write-threshold thread-safe Paolo Bonzini
2017-07-06 16:52 ` Eric Blake
2017-07-10 15:42 ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 03/11] util: use RCU accessors for notifiers Paolo Bonzini
2017-07-10 15:52 ` Stefan Hajnoczi
2017-07-10 16:06 ` Paolo Bonzini
2017-07-11 9:45 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 04/11] block: make before-write notifiers thread-safe Paolo Bonzini
2017-07-10 15:50 ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 05/11] block-backup: add reqs_lock Paolo Bonzini
2017-07-10 15:57 ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 06/11] block: add a few more notes on locking Paolo Bonzini
2017-07-10 15:57 ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 07/11] block: do not acquire AioContext in check_to_replace_node Paolo Bonzini
2017-07-10 15:58 ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 08/11] block: drain I/O around key management Paolo Bonzini
2017-07-10 16:01 ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 09/11] block/replication: do not acquire AioContext Paolo Bonzini
2017-07-06 16:38 ` [Qemu-devel] [PATCH 10/11] block: do not take AioContext around reopen Paolo Bonzini
2017-07-06 16:38 ` [Qemu-devel] [PATCH 11/11] block/snapshot: do not take AioContext lock Paolo Bonzini
2017-07-10 16:24 ` Stefan Hajnoczi
2017-07-10 16:27 ` Paolo Bonzini
2017-07-11 9:43 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-07-11 9:48 ` Paolo Bonzini
2017-07-12 10:42 ` Stefan Hajnoczi
2017-07-06 23:48 ` [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part no-reply
2017-07-07 0:06 ` Fam Zheng
2017-07-10 16:25 ` Stefan Hajnoczi
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=20170706163828.24082-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@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).