From: Jason Wang Date: Thu, 23 Apr 2015 06:21:40 +0000 (+0800) Subject: virtio-ccw: using VIRTIO_NO_VECTOR instead of 0 for invalid virtqueue X-Git-Tag: v2.4.0-rc0~139^2~17 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=955cc8c9541779e09895a9c5ccbf8ace15d884f5;p=thirdparty%2Fqemu.git virtio-ccw: using VIRTIO_NO_VECTOR instead of 0 for invalid virtqueue It's a bad idea to need to use vector 0 for invalid virtqueue. So this patch changes to using VIRTIO_NO_VECTOR instead. Cc: Michael S. Tsirkin Cc: Cornelia Huck CC: Christian Borntraeger Cc: Richard Henderson Cc: Alexander Graf Signed-off-by: Jason Wang Acked-by: Cornelia Huck Reviewed-by: Michael S. Tsirkin Signed-off-by: Michael S. Tsirkin --- diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c index d32ecafe981..0434f56637e 100644 --- a/hw/s390x/virtio-ccw.c +++ b/hw/s390x/virtio-ccw.c @@ -281,7 +281,7 @@ static int virtio_ccw_set_vqs(SubchDev *sch, uint64_t addr, uint32_t align, virtio_queue_set_addr(vdev, index, addr); if (!addr) { - virtio_queue_set_vector(vdev, index, 0); + virtio_queue_set_vector(vdev, index, VIRTIO_NO_VECTOR); } else { /* Fail if we don't have a big enough queue. */ /* TODO: Add interface to handle vring.num changing */