From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-stable@nongnu.org, Max Reitz <mreitz@redhat.com>,
stefanha@redhat.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/5] block: keep AioContext pointer in BlockBackend
Date: Tue, 27 Sep 2016 14:37:51 +0800 [thread overview]
Message-ID: <1474958276-7715-1-git-send-email-famz@redhat.com> (raw)
The first patches clean up usage of BlockBackend and changing of its (root's)
aio contexts; the last patch is an update of Stefan's previous version rebasing
on top of current master. The biggest change from the RFC is that blk_insert_bs
callers are responsible to put the BB and BDS on the same context before
calling it.
This fixes the crash triggered by "change" a scsi-cd on a virtio-scsi dataplane
device.
The new assertions in block-backend.c ensures we won't have a conflict pair of
BlockBackend users from different contextes.
Fam Zheng (4):
blockdev-mirror: Sanity check before moving target_bs AioContext
blockdev: Move BDS AioContext before inserting to BB
block: Introduce and make use of blk_new_with_root
migration: Set correct AioContext to BlockBackend
Stefan Hajnoczi (1):
block: keep AioContext pointer in BlockBackend
block/backup.c | 3 +--
block/block-backend.c | 48 +++++++++++++++++++++++++++++-----------
block/commit.c | 12 ++++------
block/mirror.c | 3 +--
blockdev.c | 42 ++++++++++++++++++++++++++---------
blockjob.c | 3 +--
hmp.c | 3 +--
hw/core/qdev-properties-system.c | 3 +--
include/sysemu/block-backend.h | 1 +
migration/block.c | 1 +
nbd/server.c | 3 +--
tests/test-blockjob.c | 3 +--
12 files changed, 79 insertions(+), 46 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-27 6:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 6:37 Fam Zheng [this message]
2016-09-27 6:37 ` [Qemu-devel] [PATCH v2 1/5] blockdev-mirror: Sanity check before moving target_bs AioContext Fam Zheng
2016-09-28 16:37 ` Max Reitz
2016-09-29 3:14 ` Fam Zheng
2016-09-27 6:37 ` [Qemu-devel] [PATCH v2 2/5] blockdev: Move BDS AioContext before inserting to BB Fam Zheng
2016-09-28 17:09 ` Max Reitz
2016-09-27 6:37 ` [Qemu-devel] [PATCH v2 3/5] block: Introduce and make use of blk_new_with_root Fam Zheng
2016-09-28 17:21 ` Max Reitz
2016-09-27 6:37 ` [Qemu-devel] [PATCH v2 4/5] migration: Set correct AioContext to BlockBackend Fam Zheng
2016-09-28 17:26 ` Max Reitz
2016-09-27 6:37 ` [Qemu-devel] [PATCH v2 5/5] block: keep AioContext pointer in BlockBackend Fam Zheng
2016-09-28 17:47 ` Max Reitz
2016-09-29 3:05 ` Fam Zheng
2016-09-29 7:47 ` Paolo Bonzini
2016-09-30 5:22 ` 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=1474958276-7715-1-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.