Message-ID: <530E9CD9.5040600@intel.com>
Date: Thu, 27 Feb 2014 10:03:05 +0800
From: Ren Qiaowei <qiaowei.ren@intel.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
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
References: <1393162071-23995-1-git-send-email-qiaowei.ren@intel.com> <1393162071-23995-2-git-send-email-qiaowei.ren@intel.com> <530E3DC9.90609@intel.com> <530E6048.9040600@zytor.com>
In-Reply-To: <530E6048.9040600@zytor.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/