[Xen-devel] One potential issue of shadow fault emulation

To:	"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Tim Deegan" <Tim.Deegan@xxxxxxxxxxxxx>
Subject:	[Xen-devel] One potential issue of shadow fault emulation
From:	"Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date:	Fri, 21 Dec 2007 22:58:49 +0800
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 21 Dec 2007 07:02:28 -0800
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:	AchD4f5fzI4GJGMHSimhR3Ka7UdWOA==
Thread-topic:	One potential issue of shadow fault emulation

Currently shadow fault handler try to emulate up to four extra
instruction for PAE guest, to reduce vmexit times.

But there is a potential issue here: Consider the second instruction is
a change to virtual TPR register. In physical environment, if the TPR
acceleration is enabled, the cpu will try to access the
VIRTUAL_APIC_PAGE_ADDR set in the VMCS. However, when we do emulation,
we didn't cope with this situation, and will access the APIC_ACCESS_ADDR
page pointed by the shadow. This is sure cause problem to guest, usually
blue screen, and this issue will happen randomly depends on the content
in the  apic access page.

So how should we cope with such situation? Stop emulation or, continue
emulate , but access the virtual APIC page? Or any better idea?

Thanks
-- Yunhong Jiang

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