From: Steven Rostedt <rostedt@goodmis.org>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
dave.hansen@linux.intel.com
Subject: Re: [PATCH 06/17] x86, mpx: trace attempts to find bounds tables
Date: Mon, 30 Mar 2015 17:29:36 -0400 [thread overview]
Message-ID: <20150330212936.GK3042@home.goodmis.org> (raw)
In-Reply-To: <20150327215303.AB02EF6C@viggo.jf.intel.com>
On Fri, Mar 27, 2015 at 02:53:03PM -0700, Dave Hansen wrote:
> b/arch/x86/include/asm/trace/mpx.h | 22 ++++++++++++++++++++++
> b/arch/x86/mm/mpx.c | 1 +
> 2 files changed, 23 insertions(+)
>
> diff -puN arch/x86/include/asm/trace/mpx.h~mpx-trace_unmap_search arch/x86/include/asm/trace/mpx.h
> --- a/arch/x86/include/asm/trace/mpx.h~mpx-trace_unmap_search 2015-03-27 14:35:05.987816914 -0700
> +++ b/arch/x86/include/asm/trace/mpx.h 2015-03-27 14:35:05.992817139 -0700
> @@ -75,6 +75,28 @@ TRACE_EVENT(mpx_unmap_zap,
> )
> );
>
> +TRACE_EVENT(mpx_unmap_search,
> +
> + TP_PROTO(unsigned long start,
> + unsigned long end),
> + TP_ARGS(start, end),
> +
> + TP_STRUCT__entry(
> + __field(unsigned long, start)
> + __field(unsigned long, end)
> + ),
> +
> + TP_fast_assign(
> + __entry->start = start;
> + __entry->end = end;
> + ),
> +
> + TP_printk("[0x%p:0x%p]",
> + (void *)__entry->start,
> + (void *)__entry->end
> + )
> +);
This event is exactly the same as the previous event. Can you use
DECLARE_EVENT_CLASS() and DEFINE_EVENT() instead?
-- Steve
> +
> #else
>
> /*
> diff -puN arch/x86/mm/mpx.c~mpx-trace_unmap_search arch/x86/mm/mpx.c
next prev parent reply other threads:[~2015-03-30 21:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 21:52 [PATCH 00/17] x86, mpx updates for 4.1 (take 3) Dave Hansen
2015-03-27 21:52 ` [PATCH 01/17] x86, fpu: wrap get_xsave_addr() to make it safer Dave Hansen
2015-03-27 21:52 ` [PATCH 02/17] x86, mpx: use new tsk_get_xsave_addr() Dave Hansen
2015-03-27 21:52 ` [PATCH 03/17] x86, mpx: trace #BR exceptions Dave Hansen
2015-03-30 21:25 ` Steven Rostedt
2015-03-30 21:33 ` Dave Hansen
2015-03-30 21:38 ` Steven Rostedt
2015-03-27 21:53 ` [PATCH 04/17] x86, mpx: trace entry to bounds exception paths Dave Hansen
2015-03-30 21:27 ` Steven Rostedt
2015-03-27 21:53 ` [PATCH 05/17] x86, mpx: trace when MPX is zapping pages Dave Hansen
2015-03-27 21:53 ` [PATCH 06/17] x86, mpx: trace attempts to find bounds tables Dave Hansen
2015-03-30 21:29 ` Steven Rostedt [this message]
2015-03-27 21:53 ` [PATCH 07/17] x86, mpx: trace allocation of new " Dave Hansen
2015-03-27 21:53 ` [PATCH 08/17] x86, mpx: boot-time disable Dave Hansen
2015-03-27 21:53 ` [PATCH 09/17] x86: make is_64bit_mm() widely available Dave Hansen
2015-03-27 21:53 ` [PATCH 10/17] x86: make __VIRTUAL_MASK safe to use on 32 bit Dave Hansen
2015-03-27 21:53 ` [PATCH 11/17] x86, mpx: we do not allocate the bounds directory Dave Hansen
2015-03-27 21:53 ` [PATCH 12/17] x86, mpx: remove redundant MPX_BNDCFG_ADDR_MASK Dave Hansen
2015-03-27 21:53 ` [PATCH 13/17] x86, mpx: Add temporary variable to reduce masking Dave Hansen
2015-03-27 21:53 ` [PATCH 14/17] x86, mpx: new directory entry to addr helper Dave Hansen
2015-03-27 21:53 ` [PATCH 15/17] x86, mpx: do 32-bit-only cmpxchg for 32-bit apps Dave Hansen
2015-03-27 21:53 ` [PATCH 16/17] x86, mpx: support 32-bit binaries on 64-bit kernel Dave Hansen
2015-03-27 21:53 ` [PATCH 17/17] x86, mpx: allow mixed binaries again Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2015-03-26 18:33 [PATCH 00/17] x86, mpx updates for 4.1 (take 2) Dave Hansen
2015-03-26 18:33 ` [PATCH 06/17] x86, mpx: trace attempts to find bounds tables Dave Hansen
2015-03-27 12:32 ` Borislav Petkov
2015-03-27 14:08 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150330212936.GK3042@home.goodmis.org \
--to=rostedt@goodmis.org \
--cc=dave.hansen@linux.intel.com \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox