Re: [RFC PATCH] KVM: Specify byte order for KVM_EXIT_MMIO

2014-01-24 Thread Paolo Bonzini
Il 24/01/2014 01:01, Peter Maydell ha scritto: +The 'data' member byte order is host kernel native endianness, regardless of +the endianness of the guest, and represents the the value as it would go on the +bus in real hardware. The host kernel should always be able to do: +type val =

Re: [RFC PATCH] KVM: Specify byte order for KVM_EXIT_MMIO

2014-01-24 Thread Alexander Graf
On 24.01.2014, at 14:09, Paolo Bonzini pbonz...@redhat.com wrote: Il 24/01/2014 01:01, Peter Maydell ha scritto: +The 'data' member byte order is host kernel native endianness, regardless of +the endianness of the guest, and represents the the value as it would go on the +bus in

Re: [RFC PATCH] KVM: Specify byte order for KVM_EXIT_MMIO

2014-01-24 Thread Victor Kamensky
On 24 January 2014 05:13, Alexander Graf ag...@suse.de wrote: On 24.01.2014, at 14:09, Paolo Bonzini pbonz...@redhat.com wrote: Il 24/01/2014 01:01, Peter Maydell ha scritto: +The 'data' member byte order is host kernel native endianness, regardless of +the endianness of the guest,

Re: [RFC PATCH] KVM: Specify byte order for KVM_EXIT_MMIO

2014-01-24 Thread Paolo Bonzini
Il 24/01/2014 16:23, Victor Kamensky ha scritto: Also if you use ints on real bus as description, you may want to clarify restrictions on mmio.len. Basically on 32 bit platform (i.e like V7 ARM) one cannot have mmio.len=8, because one cannot have 64bit value on 32bit data bus. Without such

Re: [RFC PATCH] KVM: Specify byte order for KVM_EXIT_MMIO

2014-01-24 Thread Victor Kamensky
On 24 January 2014 07:32, Paolo Bonzini pbonz...@redhat.com wrote: Il 24/01/2014 16:23, Victor Kamensky ha scritto: Also if you use ints on real bus as description, you may want to clarify restrictions on mmio.len. Basically on 32 bit platform (i.e like V7 ARM) one cannot have mmio.len=8,

Re: [RFC PATCH] KVM: Specify byte order for KVM_EXIT_MMIO

2014-01-24 Thread Victor Kamensky
On 24 January 2014 07:23, Victor Kamensky victor.kamen...@linaro.org wrote: On 24 January 2014 05:13, Alexander Graf ag...@suse.de wrote: On 24.01.2014, at 14:09, Paolo Bonzini pbonz...@redhat.com wrote: Il 24/01/2014 01:01, Peter Maydell ha scritto: +The 'data' member byte order is host

Re: [RFC PATCH] KVM: Specify byte order for KVM_EXIT_MMIO

2014-01-24 Thread Victor Kamensky
On 24 January 2014 05:13, Alexander Graf ag...@suse.de wrote: On 24.01.2014, at 14:09, Paolo Bonzini pbonz...@redhat.com wrote: Il 24/01/2014 01:01, Peter Maydell ha scritto: +The 'data' member byte order is host kernel native endianness, regardless of +the endianness of the guest,

Re: [RFC PATCH] KVM: Specify byte order for KVM_EXIT_MMIO

2014-01-23 Thread Peter Maydell
On 23 January 2014 23:46, Christoffer Dall christoffer.d...@linaro.org 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