From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH] x86_emulate adjustments
Date: Fri, 05 Jan 2007 15:04:53 +0000
Message-ID: <C1C41995.7285%keir@xensource.com>
References: <459E73C8.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <459E73C8.76E4.0078.0@novell.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 5/1/07 14:50, "Jan Beulich" <jbeulich@novell.com> wrote:

> Okay, I view this differently - if CPUs always behaved a certain way (i.e.
> REPNE
> and REPE being interchangeable as long as the instruction doesn't involve a
> comparison) or if behavior is clearly defined (REX followed by non-REX prefix,
> where the REX then simply has no effect), the decoder should behave as real
> hardware would.

Okay, I didn't realise the latter was defined behaviour but it does indeed
appear to be. And the REPE/REPNE thing makes sense.

 Thanks,
 Keir