From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/11][GIT PULL] tracing: various updates for 2.6.34
Date: Wed, 13 Jan 2010 09:26:19 +0100 [thread overview]
Message-ID: <20100113082619.GA23541@elte.hu> (raw)
In-Reply-To: <20100106231349.107649729@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Ingo,
>
> Please pull the latest tip/tracing/core tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core
>
>
> Lai Jiangshan (7):
> tracing: Have __dynamic_array() define a field
> tracing: Add print_fmt field
> tracing/syscalls: Init print_fmt for syscall events
> tracing/kprobes: Init print_fmt for kprobe events
> tracing: Use defined fields and print_fmt to print formats
> tracing: Remove show_format and related macros from TRACE_EVENT
> tracing: Consolidate protection of reader access to the ring buffer
>
> Steven Rostedt (2):
> tracing: Have syscall tracing call its own init function
> tracing: Add stack dump to trace_printk if stacktrace option is set
>
> Wolfram Sang (2):
> tracing: optimize recordmcount.pl for offsets-handling
> tracing: Use appropriate perl constructs in recordmcount.pl
>
> ----
> include/linux/ftrace_event.h | 3 +-
> include/linux/syscalls.h | 6 +-
> include/trace/ftrace.h | 161 +++++++++--------------------------------
> include/trace/syscall.h | 4 -
> kernel/trace/trace.c | 144 ++++++++++++++++++++++++++-----------
> kernel/trace/trace_events.c | 77 +++++++++++---------
> kernel/trace/trace_export.c | 87 ++++-------------------
> kernel/trace/trace_kprobe.c | 104 +++++++++++---------------
> kernel/trace/trace_syscalls.c | 106 ++++++++++++++--------------
> scripts/recordmcount.pl | 47 +++++-------
> 10 files changed, 310 insertions(+), 429 deletions(-)
Pulled, thanks a lot Steve!
Ingo
prev parent reply other threads:[~2010-01-13 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 23:13 Steven Rostedt
2010-01-06 23:13 ` [PATCH 01/11] tracing: Have __dynamic_array() define a field Steven Rostedt
2010-01-06 23:13 ` [PATCH 02/11] tracing: Add print_fmt field Steven Rostedt
2010-01-06 23:13 ` [PATCH 03/11] tracing/syscalls: Init print_fmt for syscall events Steven Rostedt
2010-01-06 23:13 ` [PATCH 04/11] tracing/kprobes: Init print_fmt for kprobe events Steven Rostedt
2010-01-06 23:13 ` [PATCH 05/11] tracing: Have syscall tracing call its own init function Steven Rostedt
2010-01-06 23:13 ` [PATCH 06/11] tracing: Use defined fields and print_fmt to print formats Steven Rostedt
2010-01-06 23:13 ` [PATCH 07/11] tracing: Remove show_format and related macros from TRACE_EVENT Steven Rostedt
2010-01-06 23:13 ` [PATCH 08/11] tracing: Consolidate protection of reader access to the ring buffer Steven Rostedt
2010-01-06 23:13 ` [PATCH 09/11] tracing: optimize recordmcount.pl for offsets-handling Steven Rostedt
2010-01-06 23:13 ` [PATCH 10/11] tracing: Use appropriate perl constructs in recordmcount.pl Steven Rostedt
2010-01-06 23:14 ` [PATCH 11/11] tracing: Add stack dump to trace_printk if stacktrace option is set Steven Rostedt
2010-01-13 8:26 ` Ingo Molnar [this message]
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=20100113082619.GA23541@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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
Powered by JetHome