qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Ritchie, Stuart" <Stuart.Ritchie@tellabs.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Para-virtualized ram-based filesystem?
Date: Fri, 15 Apr 2011 16:43:29 -0500	[thread overview]
Message-ID: <4DA8BC01.2030705@codemonkey.ws> (raw)
In-Reply-To: <C9CE0205.B91F%Stuart.Ritchie@tellabs.com>

On 04/15/2011 04:09 PM, Ritchie, Stuart wrote:
> Hi all,
>
> Has anyone looked at implementing a para-virtualized ram-based filesystem
> for qemu?  Or any similar dynamic memory mapping techniques for running
> guests?
>
> What I had in mind would be a convenient, zero-copy mechanism for sharing
> dynamically allocated, memory mapped files between host and guests.
>
> The host provides a primary memory-mapped file system (ramfs, tmpfs,
> hugetlbfs, etc), and the guest kernel and qemu use this host fs to provide
> the illusion to guest applications that the filesystem is local.
>
> The guest kernel contains a new filesystem, say call it vramfs,
> implementing the various VFS handlers for a para-virt filesystem.  These
> handlers call out to qemu, which in turn emulates them by invoking the
> required host system calls.

You can do this with ivshmem today.  You give it a path to a shared 
memory file, and then there's a path in sysfs that you can mmap() in 
userspace in the guest.

Regards,

Anthony Liguori

> Handling mmap/munmap is tricky -- but this is where the magic is.  There
> does seem to be some qemu infrastructure to dynamically map memory into a
> running system, though it may be designed for different requirements
> (e.g., device memory).
>
> I currently have the resources to work on this and am looking forward to
> contributing my work back to the community.  I would appreciate any help
> or pointers on this effort.
>
> Cheers,
> --Stuart
>
>
> ============================================================
> The information contained in this message may be privileged
> and confidential and protected from disclosure. If the reader
> of this message is not the intended recipient, or an employee
> or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that any reproduction,
> dissemination or distribution of this communication is strictly
> prohibited. If you have received this communication in error,
> please notify us immediately by replying to the message and
> deleting it from your computer. Thank you. Tellabs
> ============================================================
>
>

  reply	other threads:[~2011-04-15 21:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 21:09 [Qemu-devel] Para-virtualized ram-based filesystem? Ritchie, Stuart
2011-04-15 21:43 ` Anthony Liguori [this message]
2011-04-15 23:58   ` Ritchie, Stuart
2011-04-16  0:27     ` Brad Hards
2011-04-16  8:52       ` Stefan Hajnoczi
2011-04-16  8:54         ` Stefan Hajnoczi
2011-04-18  4:12         ` Ritchie, Stuart
2011-04-17 12:43     ` Avi Kivity
2011-04-18  3:28       ` Ritchie, Stuart
2011-04-18  6:31         ` Avi Kivity

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=4DA8BC01.2030705@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=Stuart.Ritchie@tellabs.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).