kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cam Macdonell <cam@cs.ualberta.ca>
To: Stephen Donnelly <sfdonnelly@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: R/W HG memory mappings with kvm?
Date: Thu, 9 Jul 2009 00:01:19 -0600	[thread overview]
Message-ID: <C281D880-3FBE-4041-8F6D-006F1A8562D8@cs.ualberta.ca> (raw)
In-Reply-To: <5f370d430907081501m60064c7dp23ebd4153c9050f1@mail.gmail.com>


On 8-Jul-09, at 4:01 PM, Stephen Donnelly wrote:

> On Thu, Jul 9, 2009 at 9:45 AM, Cam Macdonell<cam@cs.ualberta.ca>  
> 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




  reply	other threads:[~2009-07-09  6:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 22:41 R/W HG memory mappings with kvm? Stephen Donnelly
2009-07-06  7:38 ` Avi Kivity
2009-07-07 22:23   ` Stephen Donnelly
2009-07-08  4:36     ` Avi Kivity
2009-07-08 21:33       ` Stephen Donnelly
2009-07-09  8:10         ` Avi Kivity
2009-07-08 21:45       ` Cam Macdonell
2009-07-08 22:01         ` Stephen Donnelly
2009-07-09  6:01           ` Cam Macdonell [this message]
2009-07-09 22:38             ` Stephen Donnelly
2009-07-10 17:03               ` Cam Macdonell
2009-07-12 21:28                 ` Stephen Donnelly
2009-07-14 22:25                   ` [PATCH] Support shared memory device PCI device Cam Macdonell
     [not found]             ` <5f370d430907262256rd7f9fdalfbbec1f9492ce86@mail.gmail.com>
2009-07-27 14:48               ` R/W HG memory mappings with kvm? Cam Macdonell
2009-07-27 21:32                 ` Stephen Donnelly
2009-07-28  8:54                   ` Avi Kivity
2009-07-28 23:06                     ` Stephen Donnelly
2009-08-13  4:07                       ` Stephen Donnelly
2009-08-19 12:14                         ` Avi Kivity
2009-08-23 21:59                           ` Stephen Donnelly
2009-08-24  4:55                             ` Avi Kivity
2009-08-26 10:22                               ` Avi Kivity
2009-08-27  2:39                                 ` Stephen Donnelly
2009-08-27  2:34                               ` Stephen Donnelly
2009-08-27  4:08                                 ` Avi Kivity
2009-08-30 22:33                                   ` Stephen Donnelly
2009-08-31  8:44                                     ` Avi Kivity
2009-08-31 21:13                                       ` Stephen Donnelly
2009-09-09 12:50                                         ` Avi Kivity
2009-07-29 23:52                     ` Cam Macdonell
2009-07-30  9:31                       ` Avi Kivity
2009-09-28 18:27 Tsuyoshi Ozawa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C281D880-3FBE-4041-8F6D-006F1A8562D8@cs.ualberta.ca \
    --to=cam@cs.ualberta.ca \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=sfdonnelly@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).