From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: virtualization@lists.linux-foundation.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
rusty@rustcorp.com.au, thuth@linux.vnet.ibm.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH RFC v3 04/12] s390x/virtio-ccw: fix check for WRITE_FEAT
Date: Wed, 26 Nov 2014 18:28:35 +0100 [thread overview]
Message-ID: <1417022923-1654-5-git-send-email-cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1417022923-1654-1-git-send-email-cornelia.huck@de.ibm.com>
We need to check guest feature size, not host feature size to find
out whether we should call virtio_set_features(). This check is
possible now that vdev->guest_features is an array.
Reviewed-by: Thomas Huth <thuth@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
---
hw/s390x/virtio-ccw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
index 2f52b82..62ec852 100644
--- a/hw/s390x/virtio-ccw.c
+++ b/hw/s390x/virtio-ccw.c
@@ -399,7 +399,7 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
features.index = ldub_phys(&address_space_memory,
ccw.cda + sizeof(features.features));
features.features = ldl_le_phys(&address_space_memory, ccw.cda);
- if (features.index < ARRAY_SIZE(dev->host_features)) {
+ if (features.index < ARRAY_SIZE(vdev->guest_features)) {
virtio_set_features(vdev, features.index, features.features);
} else {
/*
--
1.7.9.5
next prev parent reply other threads:[~2014-11-26 17:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 17:28 [Qemu-devel] [PATCH RFC v3 00/12] qemu: towards virtio-1 host support Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 01/12] linux-headers/virtio_config: Update with VIRTIO_F_VERSION_1 Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 02/12] virtio: cull virtio_bus_set_vdev_features Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 03/12] virtio: support more feature bits Cornelia Huck
2014-11-26 17:28 ` Cornelia Huck [this message]
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 05/12] virtio: introduce legacy virtio devices Cornelia Huck
2014-11-26 18:46 ` Greg Kurz
2014-11-26 18:51 ` Michael S. Tsirkin
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 06/12] virtio: allow virtio-1 queue layout Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 07/12] dataplane: allow virtio-1 devices Cornelia Huck
2014-11-26 18:15 ` Greg Kurz
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 08/12] s390x/css: Add a callback for when subchannel gets disabled Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 09/12] s390x/virtio-ccw: add virtio set-revision call Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 10/12] s390x/virtio-ccw: support virtio-1 set_vq format Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 11/12] virtio-net/virtio-blk: enable virtio 1.0 Cornelia Huck
2014-11-26 18:50 ` Michael S. Tsirkin
2014-11-27 10:34 ` Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 12/12] s390x/virtio-ccw: " Cornelia Huck
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=1417022923-1654-5-git-send-email-cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=thuth@linux.vnet.ibm.com \
--cc=virtualization@lists.linux-foundation.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).