From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH 0/2] tracing/function_graph fixes for 2.6.31
Date: Tue, 28 Jul 2009 23:55:32 +0200 [thread overview]
Message-ID: <1248818134-5231-1-git-send-email-fweisbec@gmail.com> (raw)
Ingo, Thomas,
Those are two fixes for the function graph tracer for .31
The first one fixes a possible race condition between a function graph trace
reader and ring buffer writers, leading to a mixup inside an event entry, or
worst.
The second one fixes some issues in the output of the function graph tracer
while using splice on the trace_pipe file or ftrace_dump().
Both fixes should also be backported on .30 for the -stable branch.
Thanks,
Frederic.
The following changes since commit 4733fd328f14280900435d9dbae1487d110a4d56:
Benjamin Herrenschmidt (1):
mm: Remove duplicate definitions in MIPS and SH
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git tracing/fixes
Lai Jiangshan (2):
tracing: Fix invalid function_graph entry
tracing: Fix missing function_graph events when we splice_read from trace_pipe
kernel/trace/trace.c | 10 +++++++---
kernel/trace/trace_functions_graph.c | 11 +++++++++--
2 files changed, 16 insertions(+), 5 deletions(-)
next reply other threads:[~2009-07-28 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 21:55 Frederic Weisbecker [this message]
2009-07-28 21:55 ` [PATCH 1/2] tracing: Fix invalid function_graph entry Frederic Weisbecker
2009-07-28 21:55 ` [PATCH 2/2] tracing: Fix missing function_graph events when we splice_read from trace_pipe Frederic Weisbecker
2009-07-28 22:02 ` [GIT PULL] tracing/function_graph fixes for 2.6.31 Frederic Weisbecker
2009-08-04 11:58 ` [PATCH 0/2] " 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=1248818134-5231-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®