From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Patch] Qemu map cache Date: Mon, 04 Dec 2006 12:26:30 -0600 Message-ID: <45746856.5020502@linux.vnet.ibm.com> References: <666CC8FCE3247C4DA876BA979059781A5C27DD@pdsmsx401.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <666CC8FCE3247C4DA876BA979059781A5C27DD@pdsmsx401.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Cui, Dexuan" Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Cui, Dexuan wrote: > On IA32 host or IA32 PAE host, at present, generally, we can't create an > HVM guest with more than 2G memory, because generally it's almost > impossible for Qemu to find a large enough and consecutive virtual > address space to map an HVM guest's whole physical address space. > The attached patch fixes this issue using dynamic mapping based on > little blocks of memory. I have a feeling this patch is going to require quite a lot more work for V2E. Have you guys considered implementing this functionality for upstream QEMU? The Xen specific portions should be small and upstream QEMU has the same problem. Regards, Anthony Liguori > -- Dexuan Cui > > Signed-off-by: Jun Nakajima > Signed-off-by: Dexuan Cui > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel