From: Anthony PERARD <anthony.perard@citrix.com>
To: QEMU-devel <qemu-devel@nongnu.org>, Alexander Graf <agraf@suse.de>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Xen Devel <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [Qemu-devel] [PATCH V2 0/3] Enable QEMU to handle more than 2GB with Xen.
Date: Wed, 20 Jul 2011 19:17:41 +0100 [thread overview]
Message-ID: <1311185864-32745-1-git-send-email-anthony.perard@citrix.com> (raw)
Hi all,
Update on this series:
- Use a RAM address of 64bits only on 64bits targets when Xen is enable.
- Add some comment on the memory registration done for Xen.
Xen is not limited by the QEMU's virtual address space for the allocation of
the guest RAM. So even with a QEMU 32bits, a Xen guest can have more than 4 GB
of RAM.
With this serie, we will be able to run a guest with more than 4GB. The main
point is to change ram_addr_t from ulong to uin64 when QEMU is configure with
Xen. The second point is better register the memory in QEMU.
Regards,
Anthony PERARD (3):
cpu-common: Have a ram_addr_t of uint64 with Xen.
xen: Fix the memory registration to reflect of what is done by Xen.
vl.c: Check the asked ram_size later.
cpu-common.h | 8 ++++++++
exec.c | 9 +++++----
vl.c | 14 ++++++++------
xen-all.c | 29 +++++++++++++++++++++--------
4 files changed, 42 insertions(+), 18 deletions(-)
--
Anthony PERARD
next reply other threads:[~2011-07-20 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 18:17 Anthony PERARD [this message]
2011-07-20 18:17 ` [Qemu-devel] [PATCH V2 1/3] cpu-common: Have a ram_addr_t of uint64 with Xen Anthony PERARD
2011-07-20 18:17 ` [Qemu-devel] [PATCH V2 2/3] xen: Fix the memory registration to reflect of what is done by Xen Anthony PERARD
2011-07-20 18:17 ` [Qemu-devel] [PATCH V2 3/3] vl.c: Check the asked ram_size later Anthony PERARD
2011-07-27 12:53 ` Alexander Graf
2011-07-27 12:56 ` [Qemu-devel] [PATCH V2 0/3] Enable QEMU to handle more than 2GB with Xen Alexander Graf
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=1311185864-32745-1-git-send-email-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).