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

Borislav Petkov
2015-03-27T12:04:11Z

On Thu, Mar 26, 2015 at 11:33:38AM -0700, Dave Hansen wrote:
>
> From: Dave Hansen <dave.hansen@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

a tracepoint

> 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 ~ the value first.

negate
>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> ---
>
> b/arch/x86/include/asm/trace/mpx.h | 25 +++++++++++++++++++++++++
> b/arch/x86/mm/mpx.c | 2 ++
> 2 files changed, 27 insertions(+)

...

--
Regards/Gruss,
Boris.

ECO tip #101: Trim your mails when you reply.
--