From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] block: thread-safety patches for virtio-blk dataplane rerror/werror
Date: Thu, 5 Jun 2014 14:53:57 +0200 [thread overview]
Message-ID: <1401972839-25213-1-git-send-email-pbonzini@redhat.com> (raw)
With virtio-blk dataplane, I/O errors might occur while QEMU is
not in the main I/O thread. This makes the block layer's
bdrv_error_action() function thread-safe (modulo changes in
the monitor to make QMP events thread-safe too, already posted).
Thanks to Kevin for discussing v1, the ideas are based on his
input too.
v1->v2: redone, v1 should really have been an RFC
Paolo Bonzini (2):
vl: allow other threads to do qemu_system_vmstop_request
block: asynchronously stop the VM on I/O errors
block.c | 20 ++++++++++--
cpus.c | 1 +
docs/qmp/qmp-events.txt | 2 +-
include/sysemu/sysemu.h | 1 +
stubs/vm-stop.c | 7 +++-
target-lm32/op_helper.c | 2 +-
vl.c | 85 +++++++++++++++++++++++++++++++------------------
7 files changed, 82 insertions(+), 36 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-06-05 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 12:53 Paolo Bonzini [this message]
2014-06-05 12:53 ` [Qemu-devel] [PATCH v2 1/2] vl: allow other threads to do qemu_system_vmstop_request Paolo Bonzini
2014-06-19 22:18 ` Eric Blake
2014-06-05 12:53 ` [Qemu-devel] [PATCH v2 2/2] block: asynchronously stop the VM on I/O errors Paolo Bonzini
2014-06-19 22:07 ` Eric Blake
2014-06-20 3:58 ` [Qemu-devel] [PATCH v2 0/2] block: thread-safety patches for virtio-blk dataplane rerror/werror Stefan Hajnoczi
2014-06-20 6:04 ` Paolo Bonzini
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=1401972839-25213-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--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).