From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57303) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QjbiZ-0001ti-2t for qemu-devel@nongnu.org; Wed, 20 Jul 2011 14:42:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QjbiW-0007lQ-Su for qemu-devel@nongnu.org; Wed, 20 Jul 2011 14:41:58 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:16913) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QjbLM-0000KF-OZ for qemu-devel@nongnu.org; Wed, 20 Jul 2011 14:18:00 -0400 From: Anthony PERARD Date: Wed, 20 Jul 2011 19:17:41 +0100 Message-ID: <1311185864-32745-1-git-send-email-anthony.perard@citrix.com> MIME-Version: 1.0 Content-Type: text/plain Subject: [Qemu-devel] [PATCH V2 0/3] 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, 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