From: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
To: Dor Laor <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: sharing memory
Date: Fri, 07 Sep 2007 12:11:20 -0600 [thread overview]
Message-ID: <46E19448.9020803@cs.ualberta.ca> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160D7E927C-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
Dor Laor wrote:
>
> In the guest you need the matching pci driver. Currently you can you the
> attached one,
> I'm not sure if it is uptodate. Soon we'll post a device that uses
> virtio for the vmchannel.
> -Dor
Would the existing hypercall.c that is in kvm-userspace/drivers/ work as
well. What is the difference?
Thanks,
Cam
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-09-07 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 12:04 sharing memory Francesco Cipollone
2007-09-04 8:50 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D706627-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-09-04 20:03 ` Cam Macdonell
[not found] ` <46DDB9FC.4030408-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-05 7:33 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D7E927C-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-09-07 18:11 ` Cam Macdonell [this message]
[not found] ` <46E19448.9020803-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-08 22:09 ` Dor Laor
2007-09-05 20:09 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2005-01-28 18:27 Sharing Memory Adam Thorsen
2005-01-29 13:37 ` Mark Williamson
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=46E19448.9020803@cs.ualberta.ca \
--to=cam-edfdblatwiyxbbii50afww@public.gmane.org \
--cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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.