From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:35954) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qm3fO-0000Mn-OJ for qemu-devel@nongnu.org; Wed, 27 Jul 2011 08:56:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qm3fN-0005va-Cz for qemu-devel@nongnu.org; Wed, 27 Jul 2011 08:56:50 -0400 Received: from cantor2.suse.de ([195.135.220.15]:47999 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qm3fN-0005ty-3Y for qemu-devel@nongnu.org; Wed, 27 Jul 2011 08:56:49 -0400 Message-ID: <4E300B0F.5080200@suse.de> Date: Wed, 27 Jul 2011 14:56:47 +0200 From: Alexander Graf MIME-Version: 1.0 References: <1311185864-32745-1-git-send-email-anthony.perard@citrix.com> In-Reply-To: <1311185864-32745-1-git-send-email-anthony.perard@citrix.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [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: Anthony PERARD Cc: Xen Devel , QEMU-devel , Stefano Stabellini On 07/20/2011 08:17 PM, Anthony PERARD wrote: > 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(-) Thanks, applied all to xen-next. I also squashed the following patch into 3/3: diff --git a/vl.c b/vl.c index 24df37f..d8c7c01 100644 --- a/vl.c +++ b/vl.c @@ -3096,7 +3096,9 @@ int main(int argc, char **argv, char **envp) /* init the memory */ if (ram_size == 0) { ram_size = DEFAULT_RAM_SIZE * 1024 * 1024; - } else if (!xen_enabled()) { + } + + if (!xen_enabled()) { /* On 32-bit hosts, QEMU is limited by virtual address space */ if (ram_size > (2047 << 20) && HOST_LONG_BITS == 32) { fprintf(stderr, "qemu: at most 2047 MB RAM can be simulated\n"); Alex From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Subject: Re: [PATCH V2 0/3] Enable QEMU to handle more than 2GB with Xen. Date: Wed, 27 Jul 2011 14:56:47 +0200 Message-ID: <4E300B0F.5080200@suse.de> References: <1311185864-32745-1-git-send-email-anthony.perard@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1311185864-32745-1-git-send-email-anthony.perard@citrix.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Anthony PERARD Cc: Xen Devel , QEMU-devel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 07/20/2011 08:17 PM, Anthony PERARD wrote: > 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(-) Thanks, applied all to xen-next. I also squashed the following patch into 3/3: diff --git a/vl.c b/vl.c index 24df37f..d8c7c01 100644 --- a/vl.c +++ b/vl.c @@ -3096,7 +3096,9 @@ int main(int argc, char **argv, char **envp) /* init the memory */ if (ram_size == 0) { ram_size = DEFAULT_RAM_SIZE * 1024 * 1024; - } else if (!xen_enabled()) { + } + + if (!xen_enabled()) { /* On 32-bit hosts, QEMU is limited by virtual address space */ if (ram_size > (2047 << 20) && HOST_LONG_BITS == 32) { fprintf(stderr, "qemu: at most 2047 MB RAM can be simulated\n"); Alex