From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] physical memory allocation?
Date: Tue, 09 Sep 2008 11:11:25 +0200 [thread overview]
Message-ID: <48C63DBD.8040605@redhat.com> (raw)
Hi folks,
I've looked at the physical guest memory allocation code (aka
qemu_vmalloc). Reason is that I need some way to map guest memory pages
to a second location in virtual memory. Thus I need a filehandle for
the memory, so I can mmap() pages from it somewhere.
I've seen there is a phys_ram_fd variable defined in exec.c. It isn't
used anywhere though. kqemu seems to have very simliar needs, there is
some code to back guest memory using a file in /dev/shm.
How about doing that *unconditionally*, not just for kqemu?
cheers,
Gerd
next reply other threads:[~2008-09-09 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 9:11 Gerd Hoffmann [this message]
2008-09-09 12:04 ` [Qemu-devel] physical memory allocation? Paul Brook
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=48C63DBD.8040605@redhat.com \
--to=kraxel@redhat.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).