Alexander Graf wrote:
quoted text
> Or we could put in some code that tells the guest the host shm  
> architecture and only accept x86 on x86 for now. If anyone cares for  
> other combinations, they're free to implement them.
> 
> Seriously, we're looking at an interface designed for kvm here. Let's  
> please keep it as simple and fast as possible for the actual use case,  
> not some theoretically possible ones.

The concern is that a perfectly working guest image running on kvm,
the guest being some OS or app that uses this facility (_not_ a
kvm-only guest driver), is later run on qemu on a different host, and
then mostly works except for some silent data corruption.

That is not a theoretical scenario.

Well, the bit with this driver is theoretical, obviously :-)
But not the bit about moving to a different host.

-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html