[PATCH 04/17] x86, mpx: trace entry to bounds exception paths

2015-04-22 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 04/17] x86, mpx: trace entry to bounds exception paths

2015-04-22 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 04/17] x86, mpx: trace entry to bounds exception paths

2015-03-30 Thread Steven Rostedt
On Fri, Mar 27, 2015 at 02:53:00PM -0700, Dave Hansen wrote: > diff -puN arch/x86/include/asm/trace/mpx.h~x86-mpx-trace-1 > arch/x86/include/asm/trace/mpx.h > --- a/arch/x86/include/asm/trace/mpx.h~x86-mpx-trace-12015-03-27 > 14:35:05.164779793 -0700 > +++

Re: [PATCH 04/17] x86, mpx: trace entry to bounds exception paths

2015-03-30 Thread Steven Rostedt
On Fri, Mar 27, 2015 at 02:53:00PM -0700, Dave Hansen wrote: diff -puN arch/x86/include/asm/trace/mpx.h~x86-mpx-trace-1 arch/x86/include/asm/trace/mpx.h --- a/arch/x86/include/asm/trace/mpx.h~x86-mpx-trace-12015-03-27 14:35:05.164779793 -0700 +++ b/arch/x86/include/asm/trace/mpx.h

[PATCH 04/17] x86, mpx: trace entry to bounds exception paths

2015-03-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

Re: [PATCH 04/17] x86, mpx: trace entry to bounds exception paths

2015-03-27 Thread Borislav Petkov
On Thu, Mar 26, 2015 at 11:33:38AM -0700, 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

Re: [PATCH 04/17] x86, mpx: trace entry to bounds exception paths

2015-03-27 Thread Borislav Petkov
On Thu, Mar 26, 2015 at 11:33:38AM -0700, 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.

[PATCH 04/17] x86, mpx: trace entry to bounds exception paths

2015-03-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

[PATCH 04/17] x86, mpx: trace entry to bounds exception paths

2015-03-26 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 points for the case where we are passing the exception up to

[PATCH 04/17] x86, mpx: trace entry to bounds exception paths

2015-03-26 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 points for the case where we are passing