From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cam Macdonell Subject: Re: R/W HG memory mappings with kvm? Date: Thu, 9 Jul 2009 00:01:19 -0600 Message-ID: References: <5f370d430907051541o752d3dbag80d5cb251e5e4d00@mail.gmail.com> <4A51A9F0.7000909@redhat.com> <5f370d430907071523t120da246wf366dbfbbac9169b@mail.gmail.com> <4A54225F.1050703@redhat.com> <4A551387.3000702@cs.ualberta.ca> <5f370d430907081501m60064c7dp23ebd4153c9050f1@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v935.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org To: Stephen Donnelly Return-path: Received: from fleet.cs.ualberta.ca ([129.128.22.22]:37436 "EHLO fleet.cs.ualberta.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751351AbZGIGBV (ORCPT ); Thu, 9 Jul 2009 02:01:21 -0400 In-Reply-To: <5f370d430907081501m60064c7dp23ebd4153c9050f1@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 8-Jul-09, at 4:01 PM, Stephen Donnelly wrote: > On Thu, Jul 9, 2009 at 9:45 AM, Cam Macdonell > wrote: >> Hi Stephen, >> >> Here is the latest patch that supports interrupts. I am currently >> working >> on a broadcast mechanism that should be ready fairly soon. >> >> http://patchwork.kernel.org/patch/22368/ >> >> I have some test scripts that can demonstrate how to use the memory >> between >> guest/host and guest/guest. Let me know if you would like me to >> send them >> to you. > > Hi Cam, > > Thanks for the pointer. That makes perfect sense, I'm familiar with > PCI drivers so that's fine. > > Is there a corresponding qemu patch for the backend to the guest pci > driver? Oops right. For some reason I can't my driver patch in patchwork. http://kerneltrap.org/mailarchive/linux-kvm/2009/5/7/5665734 > I'm curious how the buffer memory is allocated and how BAR > accesses are handled from the host side. The memory for the device allocated as a POSIX shared memory object and then mmapped on to the allocated BAR region in Qemu's allocated memory. That's actually one spot that needs a bit of fixing by passing the already allocated memory object to qemu instead of mmapping on to it. Cam ----------------------------------------------- A. Cameron Macdonell Ph.D. Student Department of Computing Science University of Alberta cam@cs.ualberta.ca