From: Geunsik Lim <geunsik.lim@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] ftrace: Append wakeup_rt description of ftrace doc
Date: Wed, 8 Feb 2012 19:05:37 +0900 [thread overview]
Message-ID: <1328695537-15081-2-git-send-email-geunsik.lim@gmail.com> (raw)
In-Reply-To: <1328695537-15081-1-git-send-email-geunsik.lim@gmail.com>
From: Geunsik Lim <geunsik.lim@samsung.com>
Append and update the description about wakeup/wakeup_rt usage.
Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
---
Documentation/trace/ftrace.txt | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/Documentation/trace/ftrace.txt b/Documentation/trace/ftrace.txt
index 1ebc24c..03b5205 100644
--- a/Documentation/trace/ftrace.txt
+++ b/Documentation/trace/ftrace.txt
@@ -226,6 +226,13 @@ Here is the list of current tracers that may be configured.
Traces and records the max latency that it takes for
the highest priority task to get scheduled after
it has been woken up.
+ Traces all tasks as an average developer would expect.
+
+ "wakeup_rt"
+
+ Traces and records the max latency that it takes for just
+ RT tasks (as the current "wakeup" does). This is useful
+ for those interested in wake up timings of RT tasks.
"hw-branch-tracer"
--
1.7.8.1
next prev parent reply other threads:[~2012-02-08 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 10:05 [PATCH] ftrace: sched_switch plugin is deprecated Geunsik Lim
2012-02-08 10:05 ` Geunsik Lim [this message]
2012-02-10 13:15 ` [PATCH] ftrace: Append wakeup_rt description of ftrace doc Steven Rostedt
2012-02-17 13:50 ` [tip:perf/core] " tip-bot for Geunsik Lim
2012-02-17 13:50 ` [tip:perf/core] ftrace: sched_switch plugin is deprecated tip-bot for Geunsik Lim
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=1328695537-15081-2-git-send-email-geunsik.lim@gmail.com \
--to=geunsik.lim@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
--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;
as well as URLs for NNTP newsgroup(s).