[Xen-devel] [Patch] Avoid mov-from/to-cr8 crashing Xen when APIC

To:	<Keir.Fraser@xxxxxxxxxxxx>
Subject:	[Xen-devel] [Patch] Avoid mov-from/to-cr8 crashing Xen when APIC=0
From:	"Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Date:	Sat, 30 Sep 2006 08:46:43 +0800
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 29 Sep 2006 17:47:12 -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:	AcbhNpSgnLlsyleeR3aZurd/xO5mYAAmjw1QAHpYsZA=
Thread-topic:	[Xen-devel] [Patch] Avoid mov-from/to-cr8 crashing Xen when APIC=0

If APIC=0 in VMX configuration file, VLAPIC(v) in
mov_from_cr()/mov_to_cr() will be NULL, so calling
vlapic_get_reg()/vlapic_set_reg()/vlapic_update_ppr() will crash Xen.
Since a guest OS, which uses mov-from/to-cr8, requires APIC=1, we had
better only crash the related domain instead.

Thanks
Dexuan Cui

Signed-off-by: Dexuan Cui <dexuan.cui@xxxxxxxxx>

no-hvm_apic_support-crash_domain.diff
Description: no-hvm_apic_support-crash_domain.diff

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

xen-devel

[Xen-devel] [Patch] Avoid mov-from/to-cr8 crashing Xen when APIC=0