From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NuqBZ-0007YY-KB for qemu-devel@nongnu.org; Thu, 25 Mar 2010 12:45:33 -0400 Received: from [140.186.70.92] (port=51039 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NuqBP-0007SL-2Y for qemu-devel@nongnu.org; Thu, 25 Mar 2010 12:45:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NuqB7-0005Le-Ea for qemu-devel@nongnu.org; Thu, 25 Mar 2010 12:45:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48460) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NuqB6-0005Kl-SF for qemu-devel@nongnu.org; Thu, 25 Mar 2010 12:45:05 -0400 Date: Thu, 25 Mar 2010 18:40:52 +0200 From: "Michael S. Tsirkin" Message-ID: <20100325164052.GB16506@redhat.com> References: <1269497376-21903-1-git-send-email-cam@cs.ualberta.ca> <20100325091552.GB11153@redhat.com> <8286e4ee1003250918x659e87ai9e5ca7c68c23a7c3@mail.gmail.com> <4BAB8DE9.9080603@codemonkey.ws> <4BAB900F.5030104@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BAB900F.5030104@redhat.com> Subject: [Qemu-devel] Re: [PATCH v3 1/1] Shared memory uio_pci driver List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Cam Macdonell , virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, qemu-devel@nongnu.org On Thu, Mar 25, 2010 at 06:32:15PM +0200, Avi Kivity wrote: > On 03/25/2010 06:23 PM, Anthony Liguori wrote: >>> There has been previous discussion of virtio, however while virtio is >>> good for exporting guest memory, it's not ideal for importing memory >>> into a guest. >> >> virtio is a DMA-based API which means that it doesn't assume cache >> coherent shared memory. The PCI transport takes advantage of cache >> coherent shared memory but it's not strictly required. > > Aren't we violating this by not using dma_alloc_coherent() for the queues? I don't see what changing this would buys us though, unless a non-cache coherent architecture implements kvm. TCG runs everything on a single processor so there are no cache coherency issues. > -- > error compiling committee.c: too many arguments to function