qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
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: Sun, 17 Apr 2011 15:43:11 +0300	[thread overview]
Message-ID: <4DAAE05F.5050902@redhat.com> (raw)
In-Reply-To: <C9CE0E24.B9B3%Stuart.Ritchie@tellabs.com>

On 04/16/2011 02:58 AM, Ritchie, Stuart wrote:
> >
> >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.
>
> Please correct me if I am wrong, but with ivshmem you must to manage your
> world within a single, fixed size region.  I appreciate the simplicity of
> mapping the whole region all in one go, but our requirements are a bit
> different.  Even if you could pass multiple -device ivshmem instances,
> it's still a fixed environment.  Right?
>

You could place a read-only filesystem (say iso9660) in the region and 
mount it; it will then appear as a complete filesystem.

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

  parent reply	other threads:[~2011-04-17 12: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
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 [this message]
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=4DAAE05F.5050902@redhat.com \
    --to=avi@redhat.com \
    --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).