qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for 2.1] vfio: use correct runstate
Date: Fri, 27 Jun 2014 10:34:59 -0600	[thread overview]
Message-ID: <1403886899.31091.187.camel@ul30vt.home> (raw)
In-Reply-To: <1403879569-24256-1-git-send-email-pbonzini@redhat.com>

On Fri, 2014-06-27 at 16:32 +0200, Paolo Bonzini wrote:
> io-error is for block device errors; it should always be preceded
> by a BLOCK_IO_ERROR event.

Where does this requirement come from?  I only see a loose association
of IO_ERROR to disk in libvirt and none in QEMU.

>   I think vfio wants to use
> RUN_STATE_INTERNAL_ERROR instead.

But that seems to put us into an "unknown" paused state in libvirt.  An
I/O error still seems like a more appropriate state.  I'm not sure this
qualifies as a trivial patch, it is small, but subtle.  Thanks,

Alex

> 
> Cc: Alex Williamson <alex.williamson@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  hw/misc/vfio.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/misc/vfio.c b/hw/misc/vfio.c
> index 7437c2e..9d71d97 100644
> --- a/hw/misc/vfio.c
> +++ b/hw/misc/vfio.c
> @@ -3978,7 +3978,7 @@ static void vfio_err_notifier_handler(void *opaque)
>                   __func__, vdev->host.domain, vdev->host.bus,
>                   vdev->host.slot, vdev->host.function);
>  
> -    vm_stop(RUN_STATE_IO_ERROR);
> +    vm_stop(RUN_STATE_INTERNAL_ERROR);
>  }
>  
>  /*

  reply	other threads:[~2014-06-27 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 14:32 [Qemu-devel] [PATCH for 2.1] vfio: use correct runstate Paolo Bonzini
2014-06-27 16:34 ` Alex Williamson [this message]
2014-06-27 17:51   ` Paolo Bonzini
2014-06-27 18:36     ` Alex Williamson
2014-07-02 13:32     ` Eric Blake

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=1403886899.31091.187.camel@ul30vt.home \
    --to=alex.williamson@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).