On 17.12.14 10:23, Paolo Bonzini wrote: > > > On 17/12/2014 06:06, Laszlo Ersek wrote: >>>> That said, the standalone selector is used by BE platforms only, so we >>>> know that the standalone selector is always DEVICE_BIG_ENDIAN. >> This series exposes the standalone selector (as MMIO) to ARM guests as >> well; and in "Documentation/devicetree/bindings/arm/fw-cfg.txt" for the >> kernel I'm saying that the selector is little endian. >> >> Therefore I think that the standalone selector is not only (going to be) >> used by BE platforms (or I don't understand your above statement >> correctly). > > It's not going to be used only by BE platforms. But so far it is used > by BE platforms only. If you want to keep everything consistent, you > can make it (and the wide datum) BE; and swizzle data in the firmware. > Otherwise, NATIVE_ENDIAN is fine.
For the sake of keeping myself sane, I would really prefer not to have NATIVE_ENDIAN. Once you start thinking about little endian guests on PPC sharing code with little endian guests on x86 your head will start to explode otherwise. If code becomes simpler by making the mmio accessors BIG_ENDIAN, that's fine with me as well. Alex
