All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] block: thread-safety patches for virtio-blk dataplane rerror/werror
Date: Fri, 20 Jun 2014 02:04:21 -0400 (EDT)	[thread overview]
Message-ID: <1786543805.29668336.1403244261041.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20140620035859.GA11029@stefanha-thinkpad.redhat.com>



----- Messaggio originale -----
> Da: "Stefan Hajnoczi" <stefanha@redhat.com>
> A: "Paolo Bonzini" <pbonzini@redhat.com>
> Cc: qemu-devel@nongnu.org, famz@redhat.com, kwolf@redhat.com
> Inviato: Venerdì, 20 giugno 2014 5:58:59
> Oggetto: Re: [PATCH v2 0/2] block: thread-safety patches for virtio-blk dataplane rerror/werror
> 
> On Thu, Jun 05, 2014 at 02:53:57PM +0200, Paolo Bonzini wrote:
> > 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(-)
> 
> Thanks, applied to my block tree:
> https://github.com/stefanha/qemu/commits/block

Hi Stefan, both patches actually will need rebasing on top of the
QAPI event series from Wenchao.  I can resend it next week.

Paolo

      reply	other threads:[~2014-06-20  6:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 12:53 [Qemu-devel] [PATCH v2 0/2] block: thread-safety patches for virtio-blk dataplane rerror/werror Paolo Bonzini
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 [this message]

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=1786543805.29668336.1403244261041.JavaMail.zimbra@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 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.