All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 00/10] tracing: Addition of trace event trigeers
Date: Mon, 23 Dec 2013 16:38:10 -0500	[thread overview]
Message-ID: <20131223213810.967436536@goodmis.org> (raw)

This is Tom Zanussi's addition of trace event triggers.

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: 05741e383228a79eeec83644181255d2171f9f7c


Steven Rostedt (Red Hat) (3):
      tracing: Move ftrace_event_file() out of DYNAMIC_FTRACE ifdef
      tracing: Add generic tracing_lseek() function
      tracing: Fix rcu handling of event_trigger_data filter field

Tom Zanussi (7):
      tracing: Add basic event trigger framework
      tracing: Add 'traceon' and 'traceoff' event trigger commands
      tracing: Add 'snapshot' event trigger command
      tracing: Add 'stacktrace' event trigger command
      tracing: Add 'enable_event' and 'disable_event' event trigger commands
      tracing: Add and use generic set_trigger_filter() implementation
      tracing: Add documentation for trace event triggers

----
 Documentation/trace/events.txt      |  207 +++++
 include/linux/ftrace.h              |    2 -
 include/linux/ftrace_event.h        |   22 +
 include/trace/ftrace.h              |   44 +-
 kernel/trace/Makefile               |    1 +
 kernel/trace/ftrace.c               |   25 +-
 kernel/trace/trace.c                |   47 +-
 kernel/trace/trace.h                |  193 +++++
 kernel/trace/trace_events.c         |   49 +-
 kernel/trace/trace_events_filter.c  |   12 +
 kernel/trace/trace_events_trigger.c | 1411 +++++++++++++++++++++++++++++++++++
 kernel/trace/trace_stack.c          |    2 +-
 kernel/trace/trace_syscalls.c       |   42 +-
 13 files changed, 1994 insertions(+), 63 deletions(-)

             reply	other threads:[~2013-12-23 21:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 21:38 Steven Rostedt [this message]
2013-12-23 21:38 ` [for-next][PATCH 01/10] tracing: Add basic event trigger framework Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 02/10] tracing: Add traceon and traceoff event trigger commands Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 03/10] tracing: Add snapshot event trigger command Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 04/10] tracing: Add stacktrace " Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 05/10] tracing: Add enable_event and disable_event event trigger commands Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 06/10] tracing: Move ftrace_event_file() out of DYNAMIC_FTRACE ifdef Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 07/10] tracing: Add and use generic set_trigger_filter() implementation Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 08/10] tracing: Add documentation for trace event triggers Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 09/10] tracing: Add generic tracing_lseek() function Steven Rostedt
2013-12-23 21:38 ` [for-next][PATCH 10/10] tracing: Fix rcu handling of event_trigger_data filter field Steven Rostedt

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=20131223213810.967436536@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tom.zanussi@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.