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 0/4] [GIT PULL] tracing: updates
Date: Wed, 12 May 2010 21:21:10 -0400 [thread overview]
Message-ID: <20100513012110.558313399@goodmis.org> (raw)
Ingo,
This is based off of the last pull request I sent.
Please pull the latest tip/tracing/core-1 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/core-1
Carsten Emde (1):
tracing/sched: Fix task states in sched switch event
Li Zefan (1):
tracing: Fix function declarations if !CONFIG_STACKTRACE
Steven Rostedt (2):
tracing: Allow mmio tracer to display trace_printk() and other events
tracing: Update branch trace to new event API
----
fs/proc/array.c | 25 +++++++++++++------------
include/linux/sched.h | 38 ++++++++++++++++++++++++++++++++++++--
include/trace/events/sched.h | 12 +++++++++---
kernel/trace/trace.h | 4 ++--
kernel/trace/trace_branch.c | 8 ++++++--
kernel/trace/trace_mmiotrace.c | 3 ++-
6 files changed, 68 insertions(+), 22 deletions(-)
next reply other threads:[~2010-05-13 1:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 1:21 Steven Rostedt [this message]
2010-05-13 1:21 ` [PATCH 1/4] tracing: Fix function declarations if !CONFIG_STACKTRACE Steven Rostedt
2010-05-13 1:21 ` [PATCH 2/4] tracing/sched: Fix task states in sched switch event Steven Rostedt
2010-05-13 6:15 ` Ingo Molnar
2010-05-13 1:21 ` [PATCH 3/4] tracing: Allow mmio tracer to display trace_printk() and other events Steven Rostedt
2010-05-13 8:54 ` Pekka Paalanen
2010-05-13 12:15 ` Steven Rostedt
2010-05-13 12:29 ` Pekka Paalanen
2010-05-13 15:11 ` Steven Rostedt
2010-05-13 19:42 ` Steven Rostedt
2010-05-15 7:46 ` Pekka Paalanen
2010-05-16 1:29 ` Steven Rostedt
2010-05-13 1:21 ` [PATCH 4/4] tracing: Update branch trace to new event API 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=20100513012110.558313399@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 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.