Configure the queues to follow the guest endianness, and make sure
the configuration space is doing the same.

Signed-off-by: Marc Zyngier <marc.zyng...@arm.com>
---
 tools/kvm/virtio/9p.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tools/kvm/virtio/9p.c b/tools/kvm/virtio/9p.c
index 847eddb..9073a1e 100644
--- a/tools/kvm/virtio/9p.c
+++ b/tools/kvm/virtio/9p.c
@@ -1252,8 +1252,10 @@ static u32 get_host_features(struct kvm *kvm, void *dev)
 static void set_guest_features(struct kvm *kvm, void *dev, u32 features)
 {
        struct p9_dev *p9dev = dev;
+       struct virtio_9p_config *conf = p9dev->config;
 
        p9dev->features = features;
+       conf->tag_len = virtio_host_to_guest_u16(&p9dev->vdev, conf->tag_len);
 }
 
 static int init_vq(struct kvm *kvm, void *dev, u32 vq, u32 page_size, u32 
align,
@@ -1272,6 +1274,7 @@ static int init_vq(struct kvm *kvm, void *dev, u32 vq, 
u32 page_size, u32 align,
        job             = &p9dev->jobs[vq];
 
        vring_init(&queue->vring, VIRTQUEUE_NUM, p, align);
+       virtio_init_device_vq(&p9dev->vdev, queue);
 
        *job            = (struct p9_dev_job) {
                .vq             = queue,
-- 
1.8.3.4

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to