From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Jason Baron <jbaron@redhat.com>
Subject: [PATCH 0/5] [GIT PULL] tracing: print event flags and symbols
Date: Wed, 20 May 2009 23:17:11 -0400 [thread overview]
Message-ID: <20090521031711.494593605@goodmis.org> (raw)
Ingo,
Please pull the latest tip/tracing/ftrace-1 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/ftrace-1
Steven Rostedt (5):
tracing: add __print_flags for events
tracing: add previous task state info to sched switch event
tracing: add flag output for kmem events
tracing: add __print_symbolic to trace events
tracing: convert irq events to use __print_symbolic
----
include/linux/ftrace_event.h | 16 ++++++++++-
include/trace/events/irq.h | 23 +++++++++++----
include/trace/events/kmem.h | 53 ++++++++++++++++++++++++++++++-----
include/trace/events/sched.h | 9 +++++-
include/trace/ftrace.h | 22 ++++++++++++++
kernel/trace/trace_output.c | 63 ++++++++++++++++++++++++++++++++++++++++++
6 files changed, 170 insertions(+), 16 deletions(-)
--
next reply other threads:[~2009-05-21 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 3:17 Steven Rostedt [this message]
2009-05-21 3:17 ` [PATCH 1/5] tracing: add __print_flags for events Steven Rostedt
2009-05-21 3:17 ` [PATCH 2/5] tracing: add previous task state info to sched switch event Steven Rostedt
2009-05-21 3:17 ` [PATCH 3/5] tracing: add flag output for kmem events Steven Rostedt
2009-05-21 3:17 ` [PATCH 4/5] tracing: add __print_symbolic to trace events Steven Rostedt
2009-05-21 3:17 ` [PATCH 5/5] tracing: convert irq events to use __print_symbolic Steven Rostedt
2009-05-21 5:35 ` Li Zefan
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=20090521031711.494593605@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jbaron@redhat.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