WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-devel] [PATCH][IA64] Fix Qemu memory access beyond 3G

To: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][IA64] Fix Qemu memory access beyond 3G
From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
Date: Fri, 4 Aug 2006 10:53:54 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 Aug 2006 02:54:21 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CwWVbyM4Y1j/gWU6oZghE/XpRw4QlwpM9n4F10etD4NaGRUpVso5mxt6AMkCewxSogGiMZryooYqiFD4amKW4FDGivk8+is38AmzxACCMeU0g7lNEjEnECBA4akAg5lfE6tEcYPHLf31oKR7HwqCSHvA0BzFy7gAcGDoaWCRFCY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <CA502B3E9EE27B4490C87C12E3C7C8510B25FC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CA502B3E9EE27B4490C87C12E3C7C8510B25FC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 8/3/06, Zhang, Xiantao <xiantao.zhang@xxxxxxxxx> wrote:
This patch intends to fix memory access beyond 3G for VTi domain.
Currently VTi's memory beyond 3G was moved to 4G at build time. So it
should be mapped correctly in qemu. If not, it will cause qemu's
segmentation fault when guest use memory beyond 4G for DMA.

Applied, thanks!

   christian

Signed-off-by: Zhang Xiantao <xiantao.zhang@xxxxxxxxx>
Thanks & Best Regards
-Xiantao

OTC,Intel Corporation



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel





_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>