public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 00/10] [GIT PULL] tracing: various updates
Date: Tue, 02 Jun 2009 00:43:15 -0400	[thread overview]
Message-ID: <20090602044315.439593107@goodmis.org> (raw)


Ingo,

Please pull the latest tip/tracing/ftrace-2 tree, which can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/ftrace-2


Li Zefan (3):
      tracing/events: fix a typo in __string() format output
      tracing/events: put TP_fast_assign into braces
      tracing/events: introduce __dynamic_array()

Steven Rostedt (6):
      ftrace: add kernel command line function filtering
      tracing: fix config options to not show when automatically selected
      tracing: combine the default tracers into one config
      tracing: remove redundant SOFTIRQ from softirq event traces
      tracing: make trace pipe recognize latency format flag
      ftrace: do not profile functions when disabled

Steven Whitehouse (1):
      tracing: add exports to use __print_symbolic and __print_flags from a module

----
 Documentation/kernel-parameters.txt |   17 ++++-
 include/linux/ftrace_event.h        |    2 +-
 include/trace/events/irq.h          |   24 +++---
 include/trace/ftrace.h              |  126 +++++++++++++++++++++++++----------
 kernel/trace/Kconfig                |   60 ++++++++--------
 kernel/trace/ftrace.c               |   50 +++++++++++++-
 kernel/trace/trace.c                |    3 +
 kernel/trace/trace_events_filter.c  |    6 +-
 kernel/trace/trace_output.c         |    3 +
 9 files changed, 205 insertions(+), 86 deletions(-)
-- 

             reply	other threads:[~2009-06-02  4:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02  4:43 Steven Rostedt [this message]
2009-06-02  4:43 ` [PATCH 01/10] ftrace: add kernel command line function filtering Steven Rostedt
2009-06-02  4:43 ` [PATCH 02/10] tracing: fix config options to not show when automatically selected Steven Rostedt
2009-06-02  4:43 ` [PATCH 03/10] tracing: combine the default tracers into one config Steven Rostedt
2009-06-02  4:43 ` [PATCH 04/10] tracing/events: fix a typo in __string() format output Steven Rostedt
2009-06-02  4:43 ` [PATCH 05/10] tracing/events: put TP_fast_assign into braces Steven Rostedt
2009-06-02  4:43 ` [PATCH 06/10] tracing/events: introduce __dynamic_array() Steven Rostedt
2009-06-02  4:43 ` [PATCH 07/10] tracing: add exports to use __print_symbolic and __print_flags from a module Steven Rostedt
2009-06-02  4:43 ` [PATCH 08/10] tracing: remove redundant SOFTIRQ from softirq event traces Steven Rostedt
2009-06-02  4:43 ` [PATCH 09/10] tracing: make trace pipe recognize latency format flag Steven Rostedt
2009-06-02  4:43 ` [PATCH 10/10] ftrace: do not profile functions when disabled Steven Rostedt
2009-06-02  8:30 ` [PATCH 00/10] [GIT PULL] tracing: various updates Ingo Molnar
2009-06-02  9:28   ` Ingo Molnar
2009-06-02 12:51     ` 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=20090602044315.439593107@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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