[Xen-devel] Re: issues with movnti emulation

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

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