On Sat, 14 Aug 2010 09:04:19 pm Alexander Graf wrote: > > Am 06.08.2010 um 11:34 schrieb "Ira W. Snyder" <iws@xxxxxxxxxxxxxxxx>: > > This problem is not limited to my new use of virtio. Virtio is > > completely useless in a relatively common virtualization scenario: > > x86 host with qemu-ppc guest. Or any other big endian guest system. > > This one actually works because we know that we're building for a BE guest. > But I agree that it's a mess and clearly a very incorrect design decision. Yes, since you need to know the guest's endian to virtualize it, the correct interpretation of the virtio ring seemed the least problem. Perhaps I went overboard in simplification here, but it seemed pure legacy. If we did a virtio2, as has been suggested, it would be possible to address this. You could of course do a hack where you detect the ring endianness the first time they use it (based on avail.flags, avail.index and the descriptor it would be quite reliable in practice). Cheers, Rusty. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
