From: "Lai, Paul" <paul.c.lai@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: andrew.cooper3@citrix.com, ravi.sahita@intel.com,
xen-devel@lists.xenproject.org
Subject: Re: [Patch] x86emul: simplify prefix handling for VMFUNC
Date: Fri, 30 Sep 2016 11:13:10 -0700 [thread overview]
Message-ID: <20160930181309.GA13503@intel.com> (raw)
In-Reply-To: <57EB91CC020000780011316E@prv-mh.provo.novell.com>
On Wed, Sep 28, 2016 at 01:47:56AM -0600, Jan Beulich wrote:
> >>> On 27.09.16 at 19:43, <paul.c.lai@intel.com> wrote:
> > Finally found the vmfunc opcode page in Vol 3 30.3, VMX Instruction Reference.
> > Agreed, there's no mention of prefixes, "pfx", on this page. It appears
> > that the other VMX instructions in this section don't mention prefixes either.
> > Looking at Table A-6 "Opcode Extensions for One- and Two-Byte Opcodes":
> > vmcall, vmlaunch, vmresume, and vmxoff would need similar updating.
>
> Indeed.
>
> > I can ask for updating of the VMX instuctions to include mention of prefixes.
> > Anything else as I gather requirements?
>
> I don't think so, but of course if would be nice to get confirmed (ahead
> of the SDM update going public, which presumably will take some time)
> that for all of those presence of said prefixes will cause #UD, as that
> goes beyond stating that "they're reserved" (which is all the footnote
> says).
>
> Jan
>
Got word that there's an effort to clean up the SDM in general, and this
section in particular. Also, the word is that it'll be early next year (2017)
before something comes out. No expectation was set of when an early draft
would be available.
-Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-30 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8CA46881B83C354B99AD61C20C93EB1BE6C082@ORSMSX109.amr.corp.intel.com>
[not found] ` <57E176D70200007800110C54@prv-mh.provo.novell.com>
2016-09-20 22:35 ` [Patch] x86emul: simplify prefix handling for VMFUNC Lai, Paul
2016-09-21 8:39 ` Jan Beulich
2016-09-21 17:22 ` Lai, Paul
2016-09-26 18:13 ` Lai, Paul
2016-09-27 8:26 ` Jan Beulich
2016-09-27 17:43 ` Lai, Paul
2016-09-28 7:47 ` Jan Beulich
2016-09-30 18:13 ` Lai, Paul [this message]
2016-09-05 9:13 [PATCH] " Jan Beulich
2016-09-05 9:52 ` Andrew Cooper
2016-09-05 10:13 ` 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=20160930181309.GA13503@intel.com \
--to=paul.c.lai@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ravi.sahita@intel.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).