From: Alon Levy <alevy@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Dave Airlie <airlied@redhat.com>,
qemu-devel@nongnu.org, spice-devel@freedesktop.org
Subject: Re: [Qemu-devel] [Spice-devel] viewing continuous guest virtual memory as continuous in qemu
Date: Mon, 3 Oct 2011 09:49:17 +0200 [thread overview]
Message-ID: <20111003074917.GA16798@bow> (raw)
In-Reply-To: <4E889B67.1020900@redhat.com>
On Sun, Oct 02, 2011 at 07:12:07PM +0200, Avi Kivity wrote:
> On 10/02/2011 04:31 PM, Alon Levy wrote:
> >On Sun, Oct 02, 2011 at 03:24:36PM +0200, Alon Levy wrote:
> >> Hi,
> >>
> >
> >Converting qemu's ram allocation to a mmap and using remap_file_pages seems
> >like it could work. Any ideas why it wouldn't?
> >
>
> It's linux-specific. Also, does it work on anonymous memory?
Anonymous: I don't think so. I've done shm_open and mmap'ed it twice, one for the ram
and the other to do remap_file_pages on it. Couldn't figure out how to get two mmaps pointing
to the same physical memory without shm_open.
>
> I suggest using scatter-gather, though it's annoying.
>
> --
> error compiling committee.c: too many arguments to function
>
> _______________________________________________
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
next prev parent reply other threads:[~2011-10-03 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 13:24 [Qemu-devel] viewing continuous guest virtual memory as continuous in qemu Alon Levy
2011-10-02 14:31 ` [Qemu-devel] [Spice-devel] " Alon Levy
2011-10-02 17:12 ` Avi Kivity
2011-10-03 7:49 ` Alon Levy [this message]
2011-10-03 8:17 ` Yonit Halperin
2011-10-03 8:37 ` Alon Levy
2011-10-03 8:49 ` Alon Levy
2011-10-03 15:10 ` Avi Kivity
2011-10-11 11:28 ` Gerd Hoffmann
2011-10-11 12:21 ` Alon Levy
2011-10-11 13:20 ` Gerd Hoffmann
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=20111003074917.GA16798@bow \
--to=alevy@redhat.com \
--cc=airlied@redhat.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@freedesktop.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).