[PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-06-07 Thread Dave Hansen
From: Dave Hansen There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a trace point for the case where we are passing the exception up to

[PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-06-07 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a trace point for the case where we are passing

[PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-27 Thread Dave Hansen
From: Dave Hansen There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a trace point for the case where we are passing the exception up to

[PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-27 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a trace point for the case where we are passing

Re: [PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-19 Thread Thomas Gleixner
On Mon, 18 May 2015, Dave Hansen wrote: > From: Dave Hansen > > There are two basic things that can happen as the result of > a bounds exception (#BR): > > 1. We allocate a new bounds table > 2. We pass up a bounds exception to userspace. > > This patch adds a trace point for the

[PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-19 Thread Dave Hansen
From: Dave Hansen There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a trace point for the case where we are passing the exception up to

[PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-19 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a trace point for the case where we are passing

Re: [PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-19 Thread Thomas Gleixner
On Mon, 18 May 2015, Dave Hansen wrote: From: Dave Hansen dave.han...@linux.intel.com There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a

Re: [PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-18 Thread Thomas Gleixner
On Mon, 18 May 2015, Dave Hansen wrote: > On 05/18/2015 01:58 PM, Thomas Gleixner wrote: > > On Fri, 8 May 2015, Dave Hansen wrote: > >> > This patch adds a trace point for the case where we are > >> > passing the exception up to userspace with a signal. > >> > > >> > We are also explicit that

Re: [PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-18 Thread Dave Hansen
On 05/18/2015 01:58 PM, Thomas Gleixner wrote: > On Fri, 8 May 2015, Dave Hansen wrote: >> > This patch adds a trace point for the case where we are >> > passing the exception up to userspace with a signal. >> > >> > We are also explicit that we're printing out the inverse of >> > the 'upper'

Re: [PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-18 Thread Thomas Gleixner
On Fri, 8 May 2015, Dave Hansen wrote: > This patch adds a trace point for the case where we are > passing the exception up to userspace with a signal. > > We are also explicit that we're printing out the inverse of > the 'upper' that we encounter. If you want to filter, for > instance, you need

Re: [PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-18 Thread Thomas Gleixner
On Fri, 8 May 2015, Dave Hansen wrote: This patch adds a trace point for the case where we are passing the exception up to userspace with a signal. We are also explicit that we're printing out the inverse of the 'upper' that we encounter. If you want to filter, for instance, you need to ~

Re: [PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-18 Thread Dave Hansen
On 05/18/2015 01:58 PM, Thomas Gleixner wrote: On Fri, 8 May 2015, Dave Hansen wrote: This patch adds a trace point for the case where we are passing the exception up to userspace with a signal. We are also explicit that we're printing out the inverse of the 'upper' that we encounter.

Re: [PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-18 Thread Thomas Gleixner
On Mon, 18 May 2015, Dave Hansen wrote: On 05/18/2015 01:58 PM, Thomas Gleixner wrote: On Fri, 8 May 2015, Dave Hansen wrote: This patch adds a trace point for the case where we are passing the exception up to userspace with a signal. We are also explicit that we're printing out

[PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-08 Thread Dave Hansen
From: Dave Hansen There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a trace point for the case where we are passing the exception up to

[PATCH 09/19] x86, mpx: trace entry to bounds exception paths

2015-05-08 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com There are two basic things that can happen as the result of a bounds exception (#BR): 1. We allocate a new bounds table 2. We pass up a bounds exception to userspace. This patch adds a trace point for the case where we are passing