On Wed, 2014-01-22 at 20:02 +0000, Peter Maydell wrote: > > Defining it as being always guest-order would mean that > userspace had to continually look at the guest CPU > endianness bit, which is annoying and awkward. > > Defining it as always host-endian order is the most > reasonable option available. It also happens to work > for the current QEMU code, which is nice.
No. Having a byte array coming in that represents what the CPU does in its current byte order means you do *NOT* need to query the endianness of the guest CPU from userspace. Ben.
