From: Cam Macdonell <cam@cs.ualberta.ca>
To: Stephen Donnelly <sfdonnelly@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: R/W HG memory mappings with kvm?
Date: Fri, 10 Jul 2009 11:03:39 -0600 [thread overview]
Message-ID: <4A57746B.4070309@cs.ualberta.ca> (raw)
In-Reply-To: <5f370d430907091538t4285f57eua8f2e0756788c0a9@mail.gmail.com>
Stephen Donnelly wrote:
> On Thu, Jul 9, 2009 at 6:01 PM, Cam Macdonell<cam@cs.ualberta.ca> wrote:
>
>>> 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
>
> Thanks for the link, I have read through the thread now. It seems very
> relevant to what I am doing. Have you found a link to your qemu-kvm
> backend patches? Or are you running your own git tree? I don't really
> know where to look.
Oops, I realize now that I passed the driver patch both times. Here is
the old patch.
http://patchwork.kernel.org/patch/22363/
What are you compiling against? the git tree or a particular version?
The above patch won't compile against the latest git tree due to changes
to how BARs are setup in Qemu. I can send you a patch for the latest
tree if you need it.
Cam
>
>>> 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.
>
> Right, I would be passing the memory in pre-allocated as well, but
> should be a relatively simple change.
>
> Regards,
> Stephen.
next prev parent reply other threads:[~2009-07-10 17:03 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
2009-07-09 22:38 ` Stephen Donnelly
2009-07-10 17:03 ` Cam Macdonell [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=4A57746B.4070309@cs.ualberta.ca \
--to=cam@cs.ualberta.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.