From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NzYIZ-0005pz-MT for qemu-devel@nongnu.org; Wed, 07 Apr 2010 12:40:15 -0400 Received: from [140.186.70.92] (port=52706 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NzYIV-0005ov-Dj for qemu-devel@nongnu.org; Wed, 07 Apr 2010 12:40:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NzYIT-0007ik-Qz for qemu-devel@nongnu.org; Wed, 07 Apr 2010 12:40:11 -0400 Received: from mail-pz0-f204.google.com ([209.85.222.204]:35523) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NzYIT-0007iW-Kt for qemu-devel@nongnu.org; Wed, 07 Apr 2010 12:40:09 -0400 Received: by pzk42 with SMTP id 42so651002pzk.4 for ; Wed, 07 Apr 2010 09:40:06 -0700 (PDT) MIME-Version: 1.0 Sender: camm@ualberta.ca In-Reply-To: References: Date: Wed, 7 Apr 2010 10:40:06 -0600 Message-ID: From: Cam Macdonell Content-Type: text/plain; charset=ISO-8859-1 Subject: [Qemu-devel] Re: [GSoC 2010][RESEND] Shared memory transport between guest(s) and host List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mohammed Gamal Cc: Avi Kivity , kvm-devel , qemu-devel@nongnu.org On Wed, Apr 7, 2010 at 5:30 AM, Mohammed Gamal wrote: > Hi, > I am interested in the "Shared memory transport between guest(s) and > host" project for GSoC 2010. The description of the project is pretty > straightforward, but I am a little bit lost on some parts: > > 1- Is there any documentation available on KVM shared memory > transport. This'd definitely help understand how inter-vm shared > memory should work. Hi Mohammed, A shared memory transport would be a new addition to the code base so there isn't anything yet "in KVM". That said, I'm working on my patch and it will hopefully be accepted soon. Frankly, while I suggested this project, I'm not sure there's enough work remaining for the full Summer. > > 2- Does the project only aim at providing a shared memory transport > between a single host and a number of guests, with the host acting as > a central node containing shared memory objects and communication > taking placde only between guests and host, or is there any kind of > guest-guest communications to be supported? If yes, how should it be > done? My patch currently supports guest-to-guest communication and guest-to-host. I'll be sending out a new version shortly. You can see if there's something you might like to add to it whether it's part of GSoC or not. Cheers, Cam