> -----Original Message-----
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Friday, December 06, 2013 9:27 PM
> To: Ren, Qiaowei
> Cc: Paolo Bonzini; H. Peter Anvin; Ingo Molnar; Thomas Gleixner;
> x...@kernel.org; linux-kernel@vger.kernel.org; qemu-de...@nongnu.org;
> k...@vger.kernel.org; Xudong Hao; Liu, Jinsong
> Subject: Re: [PATCH 1/3] x86, mpx: add documentation on Intel MPX
> 
> On Sat, Dec 07, 2013 at 02:52:54AM +0800, Qiaowei Ren wrote:
> > This patch adds the Documentation/intel_mpx.txt file with some
> > information about Intel MPX.
> >
> > Signed-off-by: Qiaowei Ren <qiaowei....@intel.com>
> > Signed-off-by: Xudong Hao <xudong....@intel.com>
> > Signed-off-by: Liu Jinsong <jinsong....@intel.com>
> > ---
> >  Documentation/intel_mpx.txt |   77
> +++++++++++++++++++++++++++++++++++++++++++
> 
> Documentation/x86/ is probably a more fitting place for this.
> 
Yes. I will move it to Documentation/x86.

> >  1 files changed, 77 insertions(+), 0 deletions(-)  create mode 100644
> > Documentation/intel_mpx.txt
> >
> > diff --git a/Documentation/intel_mpx.txt b/Documentation/intel_mpx.txt
> > new file mode 100644 index 0000000..3d947d0
> > --- /dev/null
> > +++ b/Documentation/intel_mpx.txt
> > @@ -0,0 +1,77 @@
> > +Intel(R) MPX Overview:
> > +=====================
> > +
> > +Intel(R) Memory Protection Extensions (Intel(R) MPX) is a new
> > +capability introduced into Intel Architecture. Intel MPX can increase
> > +the robustness of software when it is used in conjunction with
> > +compiler changes to check memory references, for those references
> > +whose compile-time normal intentions are usurped
> 
> That's a strange formulation, what does it actually mean? The intentions of
> references??
> 
It is from public introduction and specification, you can refer to 
http://software.intel.com/en-us/articles/introduction-to-intel-memory-protection-extensions
 

Thanks,
Qiaowei
N�����r��y����b�X��ǧv�^�)޺{.n�+����{����zX����ܨ}���Ơz�&j:+v�������zZ+��+zf���h���~����i���z��w���?�����&�)ߢf��^jǫy�m��@A�a���
0��h���i

Reply via email to