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/
Home Products Support Community News


[Xen-devel] [PATCH] Cleanup vmx vmexit handler.

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] Cleanup vmx vmexit handler.
From: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Date: Thu, 3 Aug 2006 01:09:52 +0800
Delivery-date: Wed, 02 Aug 2006 10:11:04 -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: Aca2VnhM8q/7wJUqSeeInsvg4GNgjw==
Thread-topic: [PATCH] Cleanup vmx vmexit handler.
Cleanup vmx vmexit handler.
Current code doesn't handle vmexits caused by triple fault, INIT, SIPI,
etc, which are listed in IA32 Architecture System Programming Guide 2,
Appendix I VMX Basic Exit Reasons, and calls __hvm_bug() when not
handling such cases, actually domain crash should be good enough.
Also various coding style cleanups.

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

Attachment: cleanup_vmx.patch
Description: cleanup_vmx.patch

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>