b0e5d90ebc
The vring.c code currently assumes that guest and host endianness match, which is not true for a number of cases: - emulating targets with a different endianness than the host - bi-endian targets, where the correct endianness depends on the virtio device - upcoming support for the virtio-1 standard mandates little-endian accesses even for big-endian targets and hosts Make sure to use accessors that depend on the virtio device. Note that dataplane now needs to be built per-target. Cc: Stefan Hajnoczi <stefanha@redhat.com> Cc: Paolo Bonzini <pbonzini@redhat.com> Cc: Fam Zheng <famz@redhat.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au> Tested-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Message-id: 1422289602-17874-2-git-send-email-cornelia.huck@de.ibm.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
9 lines
268 B
Makefile
9 lines
268 B
Makefile
common-obj-y += virtio-rng.o
|
|
common-obj-$(CONFIG_VIRTIO_PCI) += virtio-pci.o
|
|
common-obj-y += virtio-bus.o
|
|
common-obj-y += virtio-mmio.o
|
|
obj-$(CONFIG_VIRTIO) += dataplane/
|
|
|
|
obj-y += virtio.o virtio-balloon.o
|
|
obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o
|