From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Subject: Re: [PATCH v3] KVM: Specify byte order for KVM_EXIT_MMIO Date: Wed, 29 Jan 2014 15:31:51 +0100 Message-ID: <52E910D7.20202@suse.de> References: <1390926522-18267-1-git-send-email-christoffer.dall@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, kvmarm@lists.cs.columbia.edu, patches@linaro.org, Marc Zyngier , Peter Maydell To: Christoffer Dall Return-path: In-Reply-To: <1390926522-18267-1-git-send-email-christoffer.dall@linaro.org> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 01/28/2014 05:28 PM, Christoffer Dall wrote: > 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 > Cc: Peter Maydell > Cc: Alexander Graf > Signed-off-by: Christoffer Dall Acked-by: Alexander Graf Alex