From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cam Macdonell Subject: Re: [PATCH v2] Driver for Inter-VM shared memory device for KVM supporting interrupts. Date: Mon, 18 May 2009 10:56:53 -0600 Message-ID: <4A119355.5030206@cs.ualberta.ca> References: <1241713567-17256-1-git-send-email-cam@cs.ualberta.ca> <200905181607.32924.borntraeger@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Christian Borntraeger Return-path: Received: from fleet.cs.ualberta.ca ([129.128.22.22]:48658 "EHLO fleet.cs.ualberta.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751882AbZERQ4x (ORCPT ); Mon, 18 May 2009 12:56:53 -0400 In-Reply-To: <200905181607.32924.borntraeger@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Christian Borntraeger wrote: > Am Thursday 07 May 2009 18:26:07 schrieb Cam Macdonell: >> Driver for inter-VM shared memory device that now supports interrupts >> between two guests. The driver defines a counting semaphore and wait_event >> queue for different synchronization needs of users. Initializing the >> semaphore count, sending interrupts and waiting are implemented via ioctl >> calls. > ... >> +#include > > Sorry for the late question, but I missed your first version. Is there a way to change that code to use virtio instead of PCI? That would allow us to use this driver on s390 and maybe other virtio transports. > > Christian > Forgive my s390 ignorance, but is there a device interface in s390 that can export memory and support interrupts? I'm not opposed to virtio, but I like the simplicity of the PCI approach as well as having the memory that is shared external to any particular VM. The current approach is using a shared memory object on the host as the shared memory the VMs share. Cam > -- > 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