From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v2] Driver for Inter-VM shared memory device for KVM supporting interrupts. Date: Tue, 19 May 2009 12:10:14 +0300 Message-ID: <4A127776.9030400@redhat.com> References: <1241713567-17256-1-git-send-email-cam@cs.ualberta.ca> <200905181607.32924.borntraeger@de.ibm.com> <4A117007.7040202@redhat.com> <200905191100.14252.borntraeger@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Cam Macdonell , kvm@vger.kernel.org, Rusty Russell , Christian Ehrhardt To: =?UTF-8?B?Q2hyaXN0aWFuIEJvcm50csOkZ2Vy?= Return-path: Received: from mx2.redhat.com ([66.187.237.31]:57609 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751320AbZESJKY (ORCPT ); Tue, 19 May 2009 05:10:24 -0400 In-Reply-To: <200905191100.14252.borntraeger@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Christian Borntr=C3=A4ger wrote: >> To summarize, Anthony thinks it should use virtio, while I believe >> virtio is useful for exporting guest memory, not for importing host = memory. >> =20 > > I think the current virtio interface is not ideal for importing host = memory,=20 > but we can change that. If you look at the dcssblk driver for s390, i= t allows=20 > a guest to map shared memory segments via a diagnose (hypercall). Thi= s driver=20 > uses PCI regions to map memory. > > My point is, that the method to map memory is completely irrelevant, = we just=20 > need something like mmap/shmget between the guest and the host. We co= uld=20 > define an interface in virtio, that can be used by any transport. In = case of=20 > pci this could be a simple pci map operation.=20 > > What do you think about something like: (CCed Rusty) > =20 Exactly. --=20 error compiling committee.c: too many arguments to function