diff options
author | Christoffer Dall <christoffer.dall@linaro.org> | 2014-01-28 17:28:42 +0100 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2014-03-27 18:25:18 +0100 |
commit | 6acdb1603a7db4c1b5d91863a13d2c3f1b9188b0 (patch) | |
tree | 214ea172ecebc84f62c8ea73aa8c8d08583492fc /drivers/acpi/acpica | |
parent | KVM: vmx: fix MPX detection (diff) | |
download | linux-6acdb1603a7db4c1b5d91863a13d2c3f1b9188b0.tar.xz linux-6acdb1603a7db4c1b5d91863a13d2c3f1b9188b0.zip |
KVM: Specify byte order for KVM_EXIT_MMIO
The KVM API documentation is not clear about the semantics of the data
field on the mmio struct on the kvm_run struct.
This has become problematic when supporting ARM guests on big-endian
host systems with guests of both endianness types, because it is unclear
how the data should be exported to user space.
This should not break with existing implementations as all supported
existing implementations of known user space applications (QEMU and
kvmtools for virtio) only support default endianness of the
architectures on the host side.
Cc: Marc Zyngier <marc.zyngier@arm.com>
Cc: Peter Maydell <peter.maydell@linaro.org>
Cc: Alexander Graf <agraf@suse.de>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'drivers/acpi/acpica')
0 files changed, 0 insertions, 0 deletions