From: John Snow <jsnow@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [RFC patch 0/3] block: pause block jobs for bdrv_drain_begin/end
Date: Wed, 15 Mar 2017 20:46:00 -0400 [thread overview]
Message-ID: <20170316004603.20609-1-jsnow@redhat.com> (raw)
Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1367369#c8
It's possible to wedge QEMU if the guest tries to reset a virtio-pci
device as QEMU is also using the drive for a blockjob. This patchset
aims to allow us to safely pause/resume jobs attached to individual
nodes in a manner similar to how bdrv_drain_all_begin/end do.
Kevin suggested a DevOps approach which I've approximated here, but
I've got a number of questions before I push the point any further.
John Snow (3):
blockjob: add block_job_start_shim
block-backend: add drained_begin / drained_end ops
blockjob: add devops to blockjob backends
block/block-backend.c | 25 ++++++++++++++++++
blockjob.c | 60 +++++++++++++++++++++++++++++++++---------
include/sysemu/block-backend.h | 8 ++++++
3 files changed, 81 insertions(+), 12 deletions(-)
--
2.9.3
next reply other threads:[~2017-03-16 0:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 0:46 John Snow [this message]
2017-03-16 0:46 ` [Qemu-devel] [RFC patch 1/3] blockjob: add block_job_start_shim John Snow
2017-03-16 8:20 ` Paolo Bonzini
2017-03-16 0:46 ` [Qemu-devel] [RFC patch 2/3] block-backend: add drained_begin / drained_end ops John Snow
2017-03-16 8:25 ` Paolo Bonzini
2017-03-16 17:25 ` Kevin Wolf
2017-03-16 19:58 ` John Snow
2017-03-16 0:46 ` [Qemu-devel] [RFC patch 3/3] blockjob: add devops to blockjob backends John Snow
2017-03-16 8:28 ` Paolo Bonzini
2017-03-16 17:36 ` Kevin Wolf
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=20170316004603.20609-1-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).