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][SVM]Generate Invalid Opcode to guest for SVM instruc

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH][SVM]Generate Invalid Opcode to guest for SVM instructions in guest.
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Wed, 28 Mar 2007 16:57:18 +0200
Cc: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Delivery-date: Wed, 28 Mar 2007 07:57:16 -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: AcdxSV6Ss7q2M+wISgqVNV8Oyglt7w==
Thread-topic: [PATCH][SVM]Generate Invalid Opcode to guest for SVM instructions in guest.
When replying to a question about VM-instructions executed in the guest
environment, I realized that the SVM-code is not behaving the same as
the VMX-code, and more importantly, it allows the guest to "terminate
itself", which isn't really a good thing to do. 

Attached patch applies to c/s: 14596. 

Signed off by: Mats Petersson <mats.petersson@xxxxxxx>


Attachment: patch.vmrun_etal_UD
Description: patch.vmrun_etal_UD

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH][SVM]Generate Invalid Opcode to guest for SVM instructions in guest., Petersson, Mats <=