From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: issues with movnti emulation
Date: Fri, 21 Nov 2008 11:04:43 +0000 [thread overview]
Message-ID: <4926A3DB.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C54B4B1D.1F707%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 20.11.08 18:13 >>>
>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.
Oh, indeed - if you mean it the other way around.
>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?).
Yes, we previously saw emulation failure messages. The guest wasn't
killed because of that, however. I have to admit it's been a while since
I last looked at mmio emulation - is it eagerly trying to emulate successive
instructions, and return to native execution when emulation failed? If
not, I could neither explain why only some data got corrupted here, nor
why the guest didn't get killed.
Jan
next prev parent reply other threads:[~2008-11-21 11:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 16:38 issues with movnti emulation Jan Beulich
2008-11-20 17:13 ` Keir Fraser
2008-11-20 17:16 ` Tim Deegan
2008-11-20 17:43 ` Keir Fraser
2008-11-21 16:01 ` Tim Deegan
2008-11-24 16:18 ` Gianluca Guida
2008-11-24 15:34 ` Jan Beulich
2008-11-20 18:42 ` Kevin Wolf
2008-11-21 11:04 ` Jan Beulich [this message]
2008-11-21 11:19 ` Keir Fraser
2008-11-25 14:01 ` Gianluca Guida
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4926A3DB.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.