From: Peter Hurley <peter@hurleysoftware.com>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>
Cc: linux-kernel@vger.kernel.org, Peter Hurley <peter@hurleysoftware.com>
Subject: [PATCH] ftrace: Document ftrace command line limitations
Date: Mon, 3 Nov 2014 20:45:25 -0500 [thread overview]
Message-ID: <1415065525-8267-1-git-send-email-peter@hurleysoftware.com> (raw)
When using the function or function_graph tracers from the command
line, certain command line options have limitations.
Document that only kernel built-in functions can be filtered via
ftrace_filter= or ftrace_graph_filter=. Also document that tracer-
specific options cannot be set on the command line via trace_options.
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
---
Documentation/kernel-parameters.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 4c81a86..6f9dfa0 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1121,6 +1121,8 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
list of functions. This list can be changed at run
time by the set_ftrace_filter file in the debugfs
tracing directory.
+ Only built-in functions can be traced when specified
+ this way.
ftrace_notrace=[function-list]
[FTRACE] Do not trace the functions specified in
@@ -1134,6 +1136,8 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
function-list is a comma separated list of functions
that can be changed at run time by the
set_graph_function file in the debugfs tracing directory.
+ Only built-in functions can be traced when specified
+ this way.
ftrace_graph_notrace=[function-list]
[FTRACE] Do not trace from the functions specified in
@@ -3521,6 +3525,10 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
trace_options=stacktrace
+ Tracer-specific options are ignored when set this way.
+ For example, the 'func_stack_trace' option cannot be
+ set here.
+
See also Documentation/trace/ftrace.txt "trace options"
section.
--
2.1.1
next reply other threads:[~2014-11-04 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 1:45 Peter Hurley [this message]
2014-11-04 2:14 ` [PATCH] ftrace: Document ftrace command line limitations Steven Rostedt
2014-11-04 2:30 ` Peter Hurley
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=1415065525-8267-1-git-send-email-peter@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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