From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PULL 1/9] Revert "virtio: sync the dataplane vring state to the virtqueue before virtio_save"
Date: Tue, 28 Jun 2016 14:23:23 +0100 [thread overview]
Message-ID: <1467120211-26495-2-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1467120211-26495-1-git-send-email-stefanha@redhat.com>
This reverts commit 10a06fd65f667a972848ebbbcac11bdba931b544.
Dataplane has used the same virtqueue code as non-dataplane since
commits e24a47c5b73e04f94030e2daa356c7582aebfca2 ("virtio-scsi: do not
use vring in dataplane") and 03de2f527499ae0c6d16a379665d072345254f2c
("virtio-blk: do not use vring in dataplane"). It is no longer
necessary to stop dataplane in order to sync state since there is no
duplicated virtqueue state.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Pavel Butsykin <pbutsykin@virtuozzo.com>
Message-id: 1466503331-9831-1-git-send-email-stefanha@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
hw/block/virtio-blk.c | 5 -----
hw/scsi/virtio-scsi.c | 5 -----
2 files changed, 10 deletions(-)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index 284e646..beb4e12 100644
--- a/hw/block/virtio-blk.c
+++ b/hw/block/virtio-blk.c
@@ -795,11 +795,6 @@ static void virtio_blk_set_status(VirtIODevice *vdev, uint8_t status)
static void virtio_blk_save(QEMUFile *f, void *opaque)
{
VirtIODevice *vdev = VIRTIO_DEVICE(opaque);
- VirtIOBlock *s = VIRTIO_BLK(vdev);
-
- if (s->dataplane) {
- virtio_blk_data_plane_stop(s->dataplane);
- }
virtio_save(vdev, f);
}
diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
index 71d09d3..e8179d6 100644
--- a/hw/scsi/virtio-scsi.c
+++ b/hw/scsi/virtio-scsi.c
@@ -666,11 +666,6 @@ static void virtio_scsi_reset(VirtIODevice *vdev)
static void virtio_scsi_save(QEMUFile *f, void *opaque)
{
VirtIODevice *vdev = VIRTIO_DEVICE(opaque);
- VirtIOSCSI *s = VIRTIO_SCSI(vdev);
-
- if (s->dataplane_started) {
- virtio_scsi_dataplane_stop(s);
- }
virtio_save(vdev, f);
}
--
2.7.4
next prev parent reply other threads:[~2016-06-28 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 13:23 [Qemu-devel] [PULL 0/9] Block patches Stefan Hajnoczi
2016-06-28 13:23 ` Stefan Hajnoczi [this message]
2016-06-28 13:23 ` [Qemu-devel] [PULL 2/9] dma-helpers: dma_blk_io() cancel support Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 3/9] virtio-blk: add VirtIOBlockConf->num_queues Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 4/9] virtio-blk: multiqueue batch notify Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 5/9] virtio-blk: tell dataplane which vq to notify Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 6/9] virtio-blk: associate request with a virtqueue Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 7/9] virtio-blk: live migrate s->rq with multiqueue Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 8/9] virtio-blk: dataplane multiqueue support Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 9/9] virtio-blk: add num-queues device property Stefan Hajnoczi
2016-06-28 14:03 ` [Qemu-devel] [PULL 0/9] Block patches Peter Maydell
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=1467120211-26495-2-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=peter.maydell@linaro.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).