From: Alexander Graf <agraf@suse.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Xen Devel <xen-devel@lists.xensource.com>,
QEMU-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/5] Enable QEMU to handle more than 2GB with Xen.
Date: Mon, 18 Jul 2011 14:32:42 +0200 [thread overview]
Message-ID: <2D16ECA9-E554-499F-8ABA-5C0FF915ABA1@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1107151804420.12963@kaball-desktop>
On 15.07.2011, at 19:05, Stefano Stabellini wrote:
> On Fri, 15 Jul 2011, Anthony PERARD wrote:
>> Hi all,
>>
>> 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 (5):
>> xen: Fix xen_enabled().
>> exec.c: Use ram_addr_t in cpu_physical_memory_rw(...).
>> 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 | 13 +++++++------
>> hw/xen.h | 2 +-
>> vl.c | 14 ++++++++------
>> xen-all.c | 23 +++++++++++++++--------
>> 5 files changed, 39 insertions(+), 21 deletions(-)
>
> All the patches look good to me, just a comment on the 4th patch.
I included patches 1 and 2 in xen-next. 3 and 4 are in discussion and 5 should only be applied when the others are in :)
Alex
prev parent reply other threads:[~2011-07-18 12:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 14:32 [Qemu-devel] [PATCH 0/5] Enable QEMU to handle more than 2GB with Xen Anthony PERARD
2011-07-15 14:32 ` [Qemu-devel] [PATCH 1/5] xen: Fix xen_enabled() Anthony PERARD
2011-07-15 14:46 ` Paolo Bonzini
2011-07-18 12:43 ` Alexander Graf
2011-07-15 14:32 ` [Qemu-devel] [PATCH 2/5] exec.c: Use ram_addr_t in cpu_physical_memory_rw(...) Anthony PERARD
2011-07-15 14:46 ` Paolo Bonzini
2011-07-15 14:32 ` [Qemu-devel] [PATCH 3/5] cpu-common: Have a ram_addr_t of uint64 with Xen Anthony PERARD
2011-07-18 12:30 ` Alexander Graf
2011-07-18 14:46 ` [Qemu-devel] [Xen-devel] " Anthony PERARD
2011-07-18 19:42 ` Anthony PERARD
2011-07-15 14:32 ` [Qemu-devel] [PATCH 4/5] xen: Fix the memory registration to reflect of what is done by Xen Anthony PERARD
2011-07-15 14:55 ` Paolo Bonzini
2011-07-15 17:05 ` Stefano Stabellini
2011-07-15 17:51 ` [Qemu-devel] [Xen-devel] " Anthony PERARD
2011-07-18 11:14 ` Stefano Stabellini
2011-07-18 15:29 ` Anthony PERARD
2011-07-18 16:14 ` [Qemu-devel] " Stefano Stabellini
2011-07-15 14:32 ` [Qemu-devel] [PATCH 5/5] vl.c: Check the asked ram_size later Anthony PERARD
2011-07-15 14:52 ` Paolo Bonzini
2011-07-15 17:05 ` [Qemu-devel] [PATCH 0/5] Enable QEMU to handle more than 2GB with Xen Stefano Stabellini
2011-07-18 12:32 ` Alexander Graf [this message]
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=2D16ECA9-E554-499F-8ABA-5C0FF915ABA1@suse.de \
--to=agraf@suse.de \
--cc=anthony.perard@citrix.com \
--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).