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
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
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
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
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
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
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
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
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
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'
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
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 ~
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.
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
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
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
16 matches
Mail list logo