diff options
| author | Greg Kurz <gkurz@linux.vnet.ibm.com> | 2016-05-31 10:09:54 +0200 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2016-06-07 15:39:28 +0300 |
| commit | c02d7030c3c538312c7f464cb79b72c29a20df74 (patch) | |
| tree | 460b25c3f584db57a1aaf09ed00d7224e449a127 /contrib | |
| parent | 9f318f8f7e689b9653b42bac73047f9719a1f34e (diff) | |
| download | qemu-c02d7030c3c538312c7f464cb79b72c29a20df74.zip qemu-c02d7030c3c538312c7f464cb79b72c29a20df74.tar.gz qemu-c02d7030c3c538312c7f464cb79b72c29a20df74.tar.bz2 | |
virtio: move bi-endian target support to a single location
Paolo's recent cpu.h cleanups broke legacy virtio for ppc64 LE guests (and
arm BE guests as well, even if I have not verified that). Especially, commit
"33c11879fd42 qemu-common: push cpu.h inclusion out of qemu-common.h" has
the side-effect of silently hiding the TARGET_IS_BIENDIAN macro from the
virtio memory accessors, and thus fully disabling support of endian changing
targets.
To be sure this cannot happen again, let's gather all the bi-endian bits
where they belong in include/hw/virtio/virtio-access.h.
The changes in hw/virtio/vhost.c are safe because vhost_needs_vring_endian()
is not called on a hot path and non bi-endian targets will return false
anyway.
While here, also rename TARGET_IS_BIENDIAN to be more precise: it is only for
legacy virtio and bi-endian guests.
Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Acked-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions