From: "Lai, Paul" <paul.c.lai@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, ravi.sahita@intel.com,
andrew.cooper3@citrix.com
Subject: Re: [Patch] x86emul: simplify prefix handling for VMFUNC
Date: Tue, 20 Sep 2016 15:35:59 -0700 [thread overview]
Message-ID: <20160920223558.GA4968@intel.com> (raw)
In-Reply-To: <57E176D70200007800110C54@prv-mh.provo.novell.com>
On Tue, Sep 20, 2016 at 09:50:15AM -0600, Jan Beulich wrote:
>
> Paul, there's been no reply to
> https://lists.xenproject.org/archives/html/xen-devel/2016-09/msg00380.html
>
> Jan
>
Jan:
The refered to patch, commit a1b1572833, adds a check for vmfunc.
I look a little time to look at the SDM and finally found the reference.
The vmfunc can be found in Table A-6 "Opcode Extensions for One- and Two-
byte Opcodes by Group Number" on page A-18 Vol. 2D of the
e64-ia-32-architectures-software-developer-manual-325462.pdf.
The values for vmfunc match the values in the code.
I also took the liberty of looking at the other existing cases in the
switch statement, and can find RDTSCP and INVLPG. The CLZERO extension
value is a mystery to me.
I also tried to find the original email referred to by the URL above, but
could not in my mail archives. Somehow it did not get to me, so I'm replying
to this email (with modified subject line) and Cc'ing Andy, Ravi, and xen-devel.
-Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next parent reply other threads:[~2016-09-20 22:33 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 ` Lai, Paul [this message]
2016-09-21 8:39 ` [Patch] x86emul: simplify prefix handling for VMFUNC 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
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=20160920223558.GA4968@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).