From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:54126) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QhjSE-0003up-9a for qemu-devel@nongnu.org; Fri, 15 Jul 2011 10:33:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QhjSC-00074a-HG for qemu-devel@nongnu.org; Fri, 15 Jul 2011 10:33:21 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:14274) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QhjSC-00073w-0F for qemu-devel@nongnu.org; Fri, 15 Jul 2011 10:33:20 -0400 From: Anthony PERARD Date: Fri, 15 Jul 2011 15:32:51 +0100 Message-ID: <1310740376-13323-1-git-send-email-anthony.perard@citrix.com> MIME-Version: 1.0 Content-Type: text/plain Subject: [Qemu-devel] [PATCH 0/5] Enable QEMU to handle more than 2GB with Xen. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU-devel , Alexander Graf Cc: Anthony PERARD , Xen Devel , Stefano Stabellini 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(-) -- Anthony PERARD