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
On 02/27/2014 05:19 AM, Dave Hansen wrote:
On 02/23/2014 05:27 AM, Qiaowei Ren wrote:
+The other case that generates a #BR is when a BNDSTX instruction
+attempts to save bounds to a BD entry marked as invalid. This is
+an indication that no BT exists for this entry. In this case the
+fault
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
On 02/23/2014 05:27 AM, Qiaowei Ren wrote:
> +The other case that generates a #BR is when a BNDSTX instruction
> +attempts to save bounds to a BD entry marked as invalid. This is
> +an indication that no BT exists for this entry. In this case the
> +fault handler will allocate a new BT.
Hi
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
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
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
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
On 02/23/2014 05:27 AM, Qiaowei Ren wrote:
+The other case that generates a #BR is when a BNDSTX instruction
+attempts to save bounds to a BD entry marked as invalid. This is
+an indication that no BT exists for this entry. In this case the
+fault handler will allocate a new BT.
Hi Qiaowei,
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
On 02/27/2014 05:19 AM, Dave Hansen wrote:
On 02/23/2014 05:27 AM, Qiaowei Ren wrote:
+The other case that generates a #BR is when a BNDSTX instruction
+attempts to save bounds to a BD entry marked as invalid. This is
+an indication that no BT exists for this entry. In this case the
+fault
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
This patch adds the Documentation/x86/intel_mpx.txt file with some
information about Intel MPX.
Signed-off-by: Qiaowei Ren
---
Documentation/x86/intel_mpx.txt | 239 +++
1 files changed, 239 insertions(+), 0 deletions(-)
create mode 100644
This patch adds the Documentation/x86/intel_mpx.txt file with some
information about Intel MPX.
Signed-off-by: Qiaowei Ren qiaowei@intel.com
---
Documentation/x86/intel_mpx.txt | 239 +++
1 files changed, 239 insertions(+), 0 deletions(-)
create mode
14 matches
Mail list logo
