From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
"kris.van.hees@oracle.com" <kris.van.hees@oracle.com>,
Keir Fraser <keir.xen@gmail.com>
Subject: Re: Invalid op code emulation for HVM guest and GPF
Date: Fri, 23 Mar 2012 19:38:51 +0000 [thread overview]
Message-ID: <4F6CD14B.4020701@citrix.com> (raw)
In-Reply-To: <20120323123042.5ebc0e18@mantra.us.oracle.com>
On 23/03/12 19:30, Mukesh Rathor wrote:
> On Fri, 23 Mar 2012 19:20:58 +0000
> Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>
>> Patch attached.
>>
>> Not tested, but seems logically correct.
>>
>> @Mukesh: Do you mind testing please?
>>
> Sure. Let me build xen with fix and give to Dtrace developers.
>
> thanks,
> Mueksh
Sadly, given your other email, I doubt it will work, because of the big
catch all regarding the lock prefix.
A brief scan over the Intel manuals and I cant see a case where an
incorrect LOCK prefix would cause #GPF rather than #UD.
Perhaps try changing it to EXP_UD instead of EXP_GP. (Although I make
no guarantee that this wont cause a lot of things to break.)
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2012-03-23 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 18:44 Invalid op code emulation for HVM guest and GPF Mukesh Rathor
2012-03-23 18:58 ` Andrew Cooper
2012-03-23 19:17 ` Keir Fraser
2012-03-23 19:28 ` Mukesh Rathor
2012-03-23 19:20 ` Andrew Cooper
2012-03-23 19:30 ` Mukesh Rathor
2012-03-23 19:38 ` Andrew Cooper [this message]
2012-03-23 19:58 ` Andrew Cooper
2012-03-23 20:40 ` Keir Fraser
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=4F6CD14B.4020701@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=keir.xen@gmail.com \
--cc=kris.van.hees@oracle.com \
--cc=mukesh.rathor@oracle.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.