From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NoPNz-0000Vt-VV for qemu-devel@nongnu.org; Sun, 07 Mar 2010 17:55:48 -0500 Received: from [199.232.76.173] (port=34098 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NoPNy-0000VW-ER for qemu-devel@nongnu.org; Sun, 07 Mar 2010 17:55:46 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NoPNx-0004Qi-De for qemu-devel@nongnu.org; Sun, 07 Mar 2010 17:55:46 -0500 Received: from mx20.gnu.org ([199.232.41.8]:42719) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NoPNx-0004QS-6w for qemu-devel@nongnu.org; Sun, 07 Mar 2010 17:55:45 -0500 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NoPNW-0002Wz-BG for qemu-devel@nongnu.org; Sun, 07 Mar 2010 17:55:18 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH] Inter-VM shared memory PCI device Date: Sun, 7 Mar 2010 22:53:59 +0000 References: <1267833161-25267-1-git-send-email-cam@cs.ualberta.ca> <1267833161-25267-2-git-send-email-cam@cs.ualberta.ca> In-Reply-To: <1267833161-25267-2-git-send-email-cam@cs.ualberta.ca> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201003072254.00040.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Cam Macdonell , kvm@vger.kernel.org > Support an inter-vm shared memory device that maps a shared-memory object > as a PCI device in the guest. This patch also supports interrupts between > guest by communicating over a unix domain socket. This patch applies to > the qemu-kvm repository. No. All new devices should be fully qdev based. I suspect you've also ignored a load of coherency issues, especially when not using KVM. As soon as you have shared memory in more than one host thread/process you have to worry about memory barriers. Paul