[Xen-devel] [PATCH] uses CPUID instruction virtualization to wor

To:	<xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] [PATCH] uses CPUID instruction virtualization to workaround VMXAssist 4G limit
From:	"Li, Xin B" <xin.b.li@xxxxxxxxx>
Date:	Thu, 19 Oct 2006 22:00:30 +0800
Delivery-date:	Thu, 19 Oct 2006 07:01:45 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcbzhvASviPx1SIDT46jHlJmcbJimw==
Thread-topic:	[PATCH] uses CPUID instruction virtualization to workaround VMXAssist 4G limit

uses CPUID instruction virtualization to workaround VMXAssist 4G limit.
Address space access limit in VMXAssist is 4G, because IA-32 only has 4G
virtual address space which VMXassist can use to map physical memory.
The issue is, win2k3 server with more than 4G memory will put AP GDT
above 4G, so when AP changes its mode from real mode to PAE paging mode,
the long jump instrction it uses need access AP GDT entries which
resides above 4G, but because of this constraint, it can not access GDT
and so fails boot.

Signed-off-by: Xin Li <xin.b.li@xxxxxxxxx>

vmxassist_4g.cpuid.patch
Description: vmxassist_4g.cpuid.patch

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] [PATCH] uses CPUID instruction virtualization to workaround