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>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH 0/5] [GIT PULL] tracing: Fixes for function graph and trace_printk
Date: Thu, 10 Dec 2009 08:20:59 +0100 [thread overview]
Message-ID: <20091210072059.GD16874@elte.hu> (raw)
In-Reply-To: <20091209204035.871524827@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> Ingo,
>
> This is a rework of the patches last sent. It is based on commit:
>
> c521efd1700a8c0f7ce26f011f5eaecca17fabfa
> tracing: Add pipe_close interface
>
> and starts with a fix to the cut and paste bug. I compiled each patch
> with and without CONFIG_TRACING enabled.
>
> Please pull the latest tip/tracing/core3 tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core3
>
>
> Carsten Emde (1):
> tracing: Remove comparing of NULL to va_list in trace_array_vprintk()
>
> Jiri Olsa (1):
> tracing: Fix function graph trace_pipe to properly display failed entries
>
> Johannes Berg (1):
> tracing: Add full state to trace_seq
>
> Steven Rostedt (2):
> tracing: Only call pipe_close if pipe_close is defined
> tracing: Buffer the output of seq_file in case of filled buffer
>
> ----
> include/linux/ftrace_event.h | 1 +
> include/linux/trace_seq.h | 7 +-
> kernel/trace/trace.c | 55 +++++++++--
> kernel/trace/trace_functions_graph.c | 165 +++++++++++++++++++++++++++-------
> kernel/trace/trace_output.c | 75 +++++++++++++---
> 5 files changed, 243 insertions(+), 60 deletions(-)
Pulled, thanks Steve!
Ingo
prev parent reply other threads:[~2009-12-10 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 20:40 [PATCH 0/5] [GIT PULL] tracing: Fixes for function graph and trace_printk Steven Rostedt
2009-12-09 20:40 ` [PATCH 1/5] [PATCH 1/5] tracing: Only call pipe_close if pipe_close is defined Steven Rostedt
2009-12-09 20:40 ` [PATCH 2/5] [PATCH 2/5] tracing: Buffer the output of seq_file in case of filled buffer Steven Rostedt
2009-12-09 20:40 ` [PATCH 3/5] [PATCH 3/5] tracing: Add full state to trace_seq Steven Rostedt
2009-12-09 20:40 ` [PATCH 4/5] [PATCH 4/5] tracing: Fix function graph trace_pipe to properly display failed entries Steven Rostedt
2009-12-09 20:40 ` [PATCH 5/5] [PATCH 5/5] tracing: Remove comparing of NULL to va_list in trace_array_vprintk() Steven Rostedt
2009-12-10 7:20 ` 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=20091210072059.GD16874@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.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