From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "haoxudong.hao@gmail.com" <haoxudong.hao@gmail.com>,
"keir@xen.org" <keir@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0/5] Definiation of Intel Architecture Instruction Set (new version), and MPX enable
Date: Thu, 21 Nov 2013 14:39:26 +0000 [thread overview]
Message-ID: <528E1B1E.5040803@citrix.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC8292335013D52CB@SHSMSX101.ccr.corp.intel.com>
On 21/11/13 14:13, Liu, Jinsong wrote:
> Ping?
It would help if the patches were linked to the covering thread.
~Andrew
>
> Liu, Jinsong wrote:
>> Hi,
>>
>> Intel has released new version of Intel Architecture Instruction Set
>> Extensions Programming Reference, add new features like AVX-512, MPX,
>> etc.
>> refer
>> http://download-software.intel.com/sites/default/files/319433-015.pdf
>>
>> These patch set add definiation of the new features, and enable MPX.
>> It based on Jan's patch and my ex-colleague Xudong's patch: Patch 1/5
>> fix a bug of current Xen xsave;
>> Patch 2/5 adds definiation of these new instruction set extension. It
>> also adjusts valid xcr0 checking;
>> Patch 3/5 handle MPX IA32_BNDCFGS msr;
>> Patch 4/5 expose MPX feature to HVM guest;
>> Patch 5/5 enable MPX feature to HVM guest;
>>
>> Thanks,
>> Jinsong
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-21 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 10:43 [PATCH 0/5] Definiation of Intel Architecture Instruction Set (new version), and MPX enable Liu, Jinsong
2013-11-21 14:13 ` Liu, Jinsong
2013-11-21 14:39 ` Andrew Cooper [this message]
2013-11-21 16:26 ` Jan Beulich
2013-11-22 16:31 ` Liu, Jinsong
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=528E1B1E.5040803@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=haoxudong.hao@gmail.com \
--cc=jinsong.liu@intel.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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 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.