From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] Inter-VM shared memory PCI device Date: Mon, 8 Mar 2010 09:54:56 +0000 Message-ID: <20100308095456.GC2869@shareable.org> References: <1267833161-25267-1-git-send-email-cam@cs.ualberta.ca> <1267833161-25267-2-git-send-email-cam@cs.ualberta.ca> <201003072254.00040.paul@codesourcery.com> <20100308014537.GA24024@shareable.org> <852A0015-DEAB-4FEF-862B-FDE35AEC9820@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paul Brook , "qemu-devel@nongnu.org" , Cam Macdonell , "kvm@vger.kernel.org" To: Alexander Graf Return-path: Received: from mail2.shareable.org ([80.68.89.115]:53205 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753113Ab0CHJzE (ORCPT ); Mon, 8 Mar 2010 04:55:04 -0500 Content-Disposition: inline In-Reply-To: <852A0015-DEAB-4FEF-862B-FDE35AEC9820@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Alexander Graf wrote: > 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