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>,
Shaohua Li <shaohua.li@intel.com>,
ia64 <linux-ia64@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>, Sam Ravnborg <sam@ravnborg.org>,
u.kleine-koenig@pengutronix.de
Subject: [PATCH 0/9] ftrace: updates for tip
Date: Tue, 13 Jan 2009 01:11:10 -0500 [thread overview]
Message-ID: <20090113061110.856268617@goodmis.org> (raw)
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: tip/devel
Frederic Weisbecker (2):
tracing/ftrace: separate events tracing and stats tracing engine
tracing: add a new workqueue tracer
Shaohua Li (6):
ftrace, ia64: make recordmcount destinct module compile
ftrace, ia64: explictly ignore a file in recordmcount.pl
ftrace, ia64: Add macro for ftrace_caller
ftrace, ia64: Add recordmcount for ia64
ftrace, ia64: IA64 static ftrace support
ftrace, ia64: IA64 dynamic ftrace support
Uwe Kleine-K?nig (1):
ftrace, trivial: fix typo "resgister" -> "register"
----
arch/ia64/Kconfig | 3 +
arch/ia64/include/asm/ftrace.h | 28 ++++
arch/ia64/kernel/Makefile | 5 +
arch/ia64/kernel/entry.S | 100 ++++++++++++++
arch/ia64/kernel/ftrace.c | 206 ++++++++++++++++++++++++++++
arch/ia64/kernel/ia64_ksyms.c | 6 +
include/linux/ftrace.h | 4 +
include/trace/workqueue.h | 25 ++++
kernel/trace/Kconfig | 11 ++
kernel/trace/Makefile | 1 +
kernel/trace/ftrace.c | 14 +--
kernel/trace/trace.c | 2 -
kernel/trace/trace.h | 20 ---
kernel/trace/trace_branch.c | 108 +++++++++-------
kernel/trace/trace_stat.c | 191 +++++++++++---------------
kernel/trace/trace_stat.h | 31 +++++
kernel/trace/trace_workqueue.c | 287 ++++++++++++++++++++++++++++++++++++++++
kernel/workqueue.c | 16 ++-
scripts/Makefile.build | 13 +-
scripts/recordmcount.pl | 18 ++-
20 files changed, 888 insertions(+), 201 deletions(-)
--
next reply other threads:[~2009-01-13 6:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 6:11 Steven Rostedt [this message]
2009-01-13 6:11 ` [PATCH 1/9] ftrace, ia64: make recordmcount destinct module compile Steven Rostedt
2009-01-13 6:11 ` [PATCH 2/9] ftrace, ia64: explictly ignore a file in recordmcount.pl Steven Rostedt
2009-01-13 6:11 ` [PATCH 3/9] ftrace, ia64: Add macro for ftrace_caller Steven Rostedt
2009-01-13 6:11 ` [PATCH 4/9] ftrace, ia64: Add recordmcount for ia64 Steven Rostedt
2009-01-13 6:11 ` [PATCH 5/9] ftrace, ia64: IA64 static ftrace support Steven Rostedt
2009-01-13 6:11 ` [PATCH 6/9] ftrace, ia64: IA64 dynamic " Steven Rostedt
2009-01-13 6:11 ` [PATCH 7/9] tracing/ftrace: separate events tracing and stats tracing engine Steven Rostedt
2009-01-13 6:11 ` [PATCH 8/9] tracing: add a new workqueue tracer Steven Rostedt
2009-01-13 6:11 ` [PATCH 9/9] ftrace, trivial: fix typo "resgister" -> "register" Steven Rostedt
2009-01-13 8:03 ` Uwe Kleine-König
2009-01-13 13:04 ` Steven Rostedt
2009-01-13 14:06 ` [PATCH 0/9] ftrace: updates for tip Steven Rostedt
2009-01-13 16:54 ` Steven Rostedt
2009-01-14 11:12 ` Ingo Molnar
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=20090113061110.856268617@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=shaohua.li@intel.com \
--cc=tony.luck@intel.com \
--cc=u.kleine-koenig@pengutronix.de \
/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