From: Ren Qiaowei <qiaowei.ren@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Dave Hansen <dave.hansen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] x86, mpx: add documentation on Intel MPX
Date: Thu, 27 Feb 2014 10:03:05 +0800 [thread overview]
Message-ID: <530E9CD9.5040600@intel.com> (raw)
In-Reply-To: <530E6048.9040600@zytor.com>
On 02/27/2014 05:44 AM, H. Peter Anvin wrote:
> On 02/26/2014 11:17 AM, Dave Hansen wrote:
>> On 02/23/2014 05:27 AM, Qiaowei Ren wrote:
>>> +Bounds Directory (BD) and Bounds Tables (BT) are stored in
>>> +application memory and are allocated by the application (in case
>>> +of kernel use, the structures will be in kernel memory). The
>>> +bound directory and each instance of bound table are in contiguous
>>> +linear memory.
>>
>> Hi Qiaowei,
>>
>> Does this mean that if userspace decided to map something in the way of
>> the bounds tables that it would break MPX?
>>
>> Also, in the description, could we s/linear/virtual/? Linear seems to
>> be the term that Intel likes to use in its documents, but we almost
>> universally call them virtual addresses in the kernel.
>>
>
> It might be useful to clarify, though, just so noone gets confused with
> effective addresses (offsets).
>
Ok. Some words here come from some MPX public documents. I need to go
through more carefully.
Thanks,
Qiaowei
next prev parent reply other threads:[~2014-02-27 2:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 13:27 [PATCH v5 0/3] Intel MPX support Qiaowei Ren
2014-02-23 13:27 ` [PATCH v5 1/3] x86, mpx: add documentation on Intel MPX Qiaowei Ren
2014-02-26 19:17 ` Dave Hansen
2014-02-26 20:58 ` Dave Hansen
2014-02-26 21:44 ` H. Peter Anvin
2014-02-27 2:03 ` Ren Qiaowei [this message]
2014-02-26 21:19 ` Dave Hansen
2014-02-27 1:58 ` Ren Qiaowei
2014-02-23 13:27 ` [PATCH v5 2/3] x86, mpx: hook #BR exception handler to allocate bound tables Qiaowei Ren
2014-02-24 17:27 ` Dave Hansen
2014-02-24 17:51 ` H. Peter Anvin
2014-02-25 13:34 ` Ren, Qiaowei
2014-02-23 13:27 ` [PATCH v5 3/3] x86, mpx: extend siginfo structure to include bound violation information Qiaowei Ren
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=530E9CD9.5040600@intel.com \
--to=qiaowei.ren@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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