From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Greg Kurz <groug@kaod.org>
Cc: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Kevin Wolf <kwolf@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>, Max Reitz <mreitz@redhat.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/7] virtio: avoid inappropriate QEMU termination
Date: Thu, 22 Sep 2016 10:28:07 +0200 [thread overview]
Message-ID: <20160922102807.3c3ecbac.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20160922101456.13f3b6eb@bahia.lab.toulouse-stg.fr.ibm.com>
On Thu, 22 Sep 2016 10:14:56 +0200
Greg Kurz <groug@kaod.org> wrote:
> On Thu, 22 Sep 2016 07:38:29 +0000
> "Gonglei (Arei)" <arei.gonglei@huawei.com> wrote:
> > I saw virtio_error() only handle the virtio 1.0 device, the legacy virtio device may
> > still stuck, am I right?
> >
>
> The DEVICE_NEEDS_RESET bit was introduced by the virtio 1.0 specification.
>
> http://docs.oasis-open.org/virtio/virtio/v1.0/cs04/virtio-v1.0-cs04.html#x1-100001
>
> Yes, the legacy device will stay stuck since the broken flag is set.
Yes, I fear there's nothing we can do to handle legacy devices
gracefully. If one broken device doesn't drag down the rest of the
machine with it, it's still a net win, I think.
prev parent reply other threads:[~2016-09-22 8:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 13:13 [Qemu-devel] [PATCH 0/7] virtio: avoid inappropriate QEMU termination Greg Kurz
2016-09-21 13:14 ` [Qemu-devel] [PATCH 1/7] virtio-9p: handle handle_9p_output() error Greg Kurz
2016-09-21 14:16 ` Cornelia Huck
2016-09-21 14:38 ` Greg Kurz
2016-09-21 14:43 ` Cornelia Huck
2016-09-21 14:42 ` Greg Kurz
2016-09-21 13:14 ` [Qemu-devel] [PATCH 2/7] virtio-blk: handle virtio_blk_handle_request() errors Greg Kurz
2016-09-21 14:28 ` Cornelia Huck
2016-09-21 15:01 ` Greg Kurz
2016-09-21 13:14 ` [Qemu-devel] [PATCH 3/7] virtio-net: handle virtio_net_handle_ctrl() error Greg Kurz
2016-09-21 14:30 ` Cornelia Huck
2016-09-21 15:03 ` Greg Kurz
2016-09-21 13:14 ` [Qemu-devel] [PATCH 4/7] virtio-net: handle virtio_net_receive() errors Greg Kurz
2016-09-21 14:38 ` Cornelia Huck
2016-09-21 13:14 ` [Qemu-devel] [PATCH 5/7] virtio-net: handle virtio_net_flush_tx() errors Greg Kurz
2016-09-21 13:14 ` [Qemu-devel] [PATCH 6/7] virtio-scsi: convert virtio_scsi_bad_req() to use virtio_error() Greg Kurz
2016-09-21 13:14 ` [Qemu-devel] [PATCH 7/7] virtio-scsi: handle virtio_scsi_set_config() error Greg Kurz
2016-09-21 13:35 ` [Qemu-devel] [PATCH 0/7] virtio: avoid inappropriate QEMU termination no-reply
2016-09-21 13:44 ` Greg Kurz
2016-09-21 14:01 ` Fam Zheng
2016-09-21 14:29 ` Eric Blake
2016-09-22 5:39 ` Fam Zheng
2016-09-21 14:34 ` Greg Kurz
2016-09-21 17:38 ` Michael S. Tsirkin
2016-09-21 17:35 ` Michael S. Tsirkin
2016-09-21 18:12 ` Greg Kurz
2016-09-22 1:19 ` Gonglei
2016-09-22 6:43 ` Greg Kurz
2016-09-22 6:55 ` Gonglei (Arei)
2016-09-22 7:21 ` Greg Kurz
2016-09-22 7:30 ` Gonglei (Arei)
2016-09-22 7:38 ` Gonglei (Arei)
2016-09-22 8:14 ` Greg Kurz
2016-09-22 8:28 ` Cornelia Huck [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=20160922102807.3c3ecbac.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arei.gonglei@huawei.com \
--cc=groug@kaod.org \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).