From: Borislav Petkov <bp@alien8.de>
To: "Ren, Qiaowei" <qiaowei.ren@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Xudong Hao <xudong.hao@intel.com>,
"Liu, Jinsong" <jinsong.liu@intel.com>
Subject: Re: [PATCH 1/3] x86, mpx: add documentation on Intel MPX
Date: Fri, 6 Dec 2013 17:06:08 +0100 [thread overview]
Message-ID: <20131206160607.GE6694@pd.tnic> (raw)
In-Reply-To: <9E0BE1322F2F2246BD820DA9FC397ADE014A4322@SHSMSX102.ccr.corp.intel.com>
On Fri, Dec 06, 2013 at 03:55:10PM +0000, Ren, Qiaowei wrote:
> It is from public introduction and specification, you can refer to
http://software.intel.com/en-us/articles/introduction-to-intel-memory-protection-extensions
Yep, saw it there too. Which doesn't make it any less strange :)
Btw, if you're going to quote the public documentation, why even add the
text file here? You can simply add the link above as a comment to the
code or as a oneliner somewhere in Documentation/x86/.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: "Ren, Qiaowei" <qiaowei.ren@intel.com>
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Xudong Hao <xudong.hao@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Qemu-devel] [PATCH 1/3] x86, mpx: add documentation on Intel MPX
Date: Fri, 6 Dec 2013 17:06:08 +0100 [thread overview]
Message-ID: <20131206160607.GE6694@pd.tnic> (raw)
In-Reply-To: <9E0BE1322F2F2246BD820DA9FC397ADE014A4322@SHSMSX102.ccr.corp.intel.com>
On Fri, Dec 06, 2013 at 03:55:10PM +0000, Ren, Qiaowei wrote:
> It is from public introduction and specification, you can refer to
http://software.intel.com/en-us/articles/introduction-to-intel-memory-protection-extensions
Yep, saw it there too. Which doesn't make it any less strange :)
Btw, if you're going to quote the public documentation, why even add the
text file here? You can simply add the link above as a comment to the
code or as a oneliner somewhere in Documentation/x86/.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-12-06 16:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 18:52 [PATCH 1/3] x86, mpx: add documentation on Intel MPX Qiaowei Ren
2013-12-06 18:52 ` [Qemu-devel] " Qiaowei Ren
2013-12-06 13:26 ` Borislav Petkov
2013-12-06 13:26 ` [Qemu-devel] " Borislav Petkov
2013-12-06 15:55 ` Ren, Qiaowei
2013-12-06 15:55 ` [Qemu-devel] " Ren, Qiaowei
2013-12-06 15:55 ` Ren, Qiaowei
2013-12-06 16:06 ` Borislav Petkov [this message]
2013-12-06 16:06 ` [Qemu-devel] " Borislav Petkov
2013-12-06 16:11 ` Ren, Qiaowei
2013-12-06 16:11 ` [Qemu-devel] " Ren, Qiaowei
2013-12-06 16:11 ` Ren, Qiaowei
2013-12-06 18:52 ` [PATCH 2/3] X86, mpx: Intel MPX definition Qiaowei Ren
2013-12-06 18:52 ` [Qemu-devel] " Qiaowei Ren
2013-12-06 13:33 ` Borislav Petkov
2013-12-06 13:33 ` [Qemu-devel] " Borislav Petkov
2013-12-06 15:58 ` H. Peter Anvin
2013-12-06 15:58 ` [Qemu-devel] " H. Peter Anvin
2013-12-06 18:52 ` [PATCH 3/3] X86, mpx: Intel MPX xstate feature definition Qiaowei Ren
2013-12-06 18:52 ` [Qemu-devel] " Qiaowei Ren
2013-12-06 13:46 ` Borislav Petkov
2013-12-06 13:46 ` [Qemu-devel] " Borislav Petkov
2013-12-06 16:08 ` Ren, Qiaowei
2013-12-06 16:08 ` [Qemu-devel] " Ren, Qiaowei
2013-12-06 16:08 ` Ren, Qiaowei
2013-12-06 17:23 ` H. Peter Anvin
2013-12-06 17:23 ` [Qemu-devel] " H. Peter Anvin
2013-12-06 18:55 ` Borislav Petkov
2013-12-06 18:55 ` [Qemu-devel] " Borislav Petkov
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=20131206160607.GE6694@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qiaowei.ren@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xudong.hao@intel.com \
/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.