WARNING - OLD ARCHIVES

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

xen-devel

[Xen-devel] x86_emulate(): Upon LOCK prefix for MOV, should inject #UD r

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] x86_emulate(): Upon LOCK prefix for MOV, should inject #UD rather than #GP?
From: "Liu, Eric E" <eric.e.liu@xxxxxxxxx>
Date: Thu, 20 Dec 2007 10:58:51 +0800
Delivery-date: Wed, 19 Dec 2007 18:59:46 -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: AchCtD/3n07kelioRSCaZ5nHelu8BQ==
Thread-topic: x86_emulate(): Upon LOCK prefix for MOV, should inject #UD rather than #GP?
Hi all,
        The Intel SDM(2A) says that if the LOCK prefix is used with some
instructions such as "mov" and the souce  operand is a memory operand, a
#UD may be generated, but in the x86_emulate.c there are places such as
:
             942     /* Lock prefix is allowed only on RMW instructions.
*/
             943     generate_exception_if((d & Mov) && lock_prefix,
EXC_GP);
here we inject EXC_GP but not EXC_UD, is it a bug?

--Eric (Liu, Feng)

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

<Prev in Thread] Current Thread [Next in Thread>