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/5] ftrace: updates for tip
Date: Wed, 21 Jan 2009 18:53:06 -0500 [thread overview]
Message-ID: <20090121235306.224764198@goodmis.org> (raw)
Ingo,
These patches are fixes for the wakeup tracer.
The first is a fix to the empty output you reported to me earlier.
The second is a fix for the ring buffer to not record updates
if it is disabled, otherwised you can get empty traces there too.
The third is the wakeup change to record all tasks and not just
realtime tasks. It adds a wakeup_rt tracer to record only rt tasks.
The forth is the addition of the scheduling wakeup and sched switch
output to the wakeup tracer. This is very helpful data.
The last is probably the most important, and should go into 29 as well.
I never reset the timestamps used to connect the trace stamps in
the buffers. This can cause stale stamps to appear and explains
some of the really bad timestamps in the buffer I've seen.
-- Steve
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: tip/devel
Steven Rostedt (5):
trace: do not disable wake up tracer on output of trace
ring-buffer: do not swap if recording is disabled
trace: separate out rt tasks from wakeup tracer
wakeup-tracer: show scheduling data in output
ring-buffer: reset timestamps when ring buffer is reset
----
kernel/trace/ring_buffer.c | 18 ++++++++
kernel/trace/trace.c | 2 +-
kernel/trace/trace_sched_wakeup.c | 78 ++++++++++++++++++++-----------------
3 files changed, 61 insertions(+), 37 deletions(-)
--
next reply other threads:[~2009-01-21 23:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 23:53 Steven Rostedt [this message]
2009-01-21 23:53 ` [PATCH 1/5] trace: do not disable wake up tracer on output of trace Steven Rostedt
2009-01-22 8:41 ` Ingo Molnar
2009-01-22 9:29 ` Ingo Molnar
2009-01-22 12:02 ` Steven Rostedt
2009-01-22 12:03 ` Ingo Molnar
2009-01-21 23:53 ` [PATCH 2/5] ring-buffer: do not swap if recording is disabled Steven Rostedt
2009-01-21 23:53 ` [PATCH 3/5] trace: separate out rt tasks from wakeup tracer Steven Rostedt
2009-01-21 23:53 ` [PATCH 4/5] wakeup-tracer: show scheduling data in output Steven Rostedt
2009-01-21 23:53 ` [PATCH 5/5] ring-buffer: reset timestamps when ring buffer is reset Steven Rostedt
2009-01-22 9:32 ` [PATCH 0/5] ftrace: updates for tip Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-12-03 4:50 Steven Rostedt
2008-12-03 8:11 ` Ingo Molnar
2008-12-02 20:34 [PATCH 0/5] ftrace " Steven Rostedt
2008-12-03 7:57 ` 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=20090121235306.224764198@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox