From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] x86emul: don't allow INVLPG in real mode
Date: Fri, 22 Apr 2016 17:08:44 +0100 [thread overview]
Message-ID: <571A4C8C.6090704@citrix.com> (raw)
In-Reply-To: <571A4E9F02000078000E4D15@prv-mh.provo.novell.com>
On 22/04/16 15:17, Jan Beulich wrote:
> As both INVLPG and INVLPGA have basically the same exception rules
> (leaving aside that INVLPGA requires SVME enabled, which so far isn't
> being taken care of,
We also don't appear to handle the ASID in %ecx correctly either. Yet
another item on the TODO list for nested virt.
> and that INVLPG requires ModRM.mod != 3), fold
> the handling of the two as much as possible alongside achieving the
> goal of the patch (at once doing the #UD checks pror to the #GP one,
> which ought to be more in line with how hardware does things).
>
> But please note that AMD and Intel disagree on what exceptions INVLPG
> may raise, and the more reasonable Intel variant is being followed.
Which differences?
You introduce the !in_protmode() check to the `invlpg` path. However,
both manuals agree that it should work in real mode (subject to the lock
prefix not being in use). I presume the difference is to whether it is
eligible for use in vm86 mode, where indeed Intel is stricter than AMD.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-22 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 14:17 [PATCH] x86emul: don't allow INVLPG in real mode Jan Beulich
2016-04-22 14:40 ` Wei Liu
2016-04-22 15:09 ` Jan Beulich
2016-04-22 16:08 ` Andrew Cooper [this message]
2016-04-25 7:28 ` Jan Beulich
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=571A4C8C.6090704@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).