public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ben Shelton <beshelto@vt.edu>
Cc: kvm@vger.kernel.org
Subject: Re: Sharing physical pages between virtual machines
Date: Tue, 29 May 2012 19:50:48 +0300	[thread overview]
Message-ID: <4FC4FE68.9000108@redhat.com> (raw)
In-Reply-To: <A502BE9A-9365-4DC6-B1B0-1E727DA96199@vt.edu>

On 05/29/2012 07:07 PM, Ben Shelton wrote:
> Hi all,
> 
> I work in the Real-Time Systems Lab at Virginia Tech.  We're looking at building a new OS design where multiple guest OS's run on the same machine and can communicate with each other by passing messages through shared memory regions (similar to Barrelfish, if you've seen that), and we'd like to implement it using KVM.  
> 
> We've looked at the Nahanni project, which provides a shared memory window for KVM guests via POSIX shared memory and an emulated PCI device, but the overhead would be too high for what we would like to do.  We'd like the guests to be able to write to, and to poll on, actual physical pages in memory.
> 
> It would seem that one could simply use EPT to map the same physical page into the guest physical address spaces of multiple virtual machines.  Would this be something that would be possible to do, given the way KVM dynamically maps physical pages to guests as needed?  If not, would there be a better way to go about it?
> 

That is what Nahanni does.  After the initial page fault everything
happens at memory/cache speeds.

-- 
error compiling committee.c: too many arguments to function

      reply	other threads:[~2012-05-29 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 16:07 Sharing physical pages between virtual machines Ben Shelton
2012-05-29 16:50 ` Avi Kivity [this message]

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=4FC4FE68.9000108@redhat.com \
    --to=avi@redhat.com \
    --cc=beshelto@vt.edu \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox