[Xen-devel] Re: issues with movnti emulation

To:	Jan Beulich <jbeulich@xxxxxxxxxx>
Subject:	[Xen-devel] Re: issues with movnti emulation
From:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date:	Thu, 20 Nov 2008 17:13:01 +0000
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Thu, 20 Nov 2008 09:13:47 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<4925A0AE.76E4.0078.0@xxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AclLMz3bfHxelrcmEd2DIQAWy6hiGQ==
Thread-topic:	issues with movnti emulation
User-agent:	Microsoft-Entourage/11.4.0.080122

I think the issue is that I did a bad backport to 3.3. The 'case 0xc3'
should be under twobyte_special_insn rather than twobyte_insn, right? The
two separate paths got merged into one in xen-unstable.

Of course this data corruption ought only to happen in cases where we'd
previously have failed an mmio emulation (and hence probably killed the
guest kernel?).

 -- Keir

On 20/11/08 16:38, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> We've got reports of that change causing HVM data corruption issues. While
> I can't see what's wrong with the patch, I'd suggest at least reverting it
> from
> the 3.3 tree (which is what our code is based upon) for the time being.
> 
> Jan
> 

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Re: issues with movnti emulation