mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] Add documentation for trace commands mod, traceon/traceoff
Date: Fri, 23 Apr 2010 09:55:28 -0700	[thread overview]
Message-ID: <20100423095528.668decf8.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1272039467-27413-1-git-send-email-chase.douglas@canonical.com>

On Fri, 23 Apr 2010 12:17:47 -0400 Chase Douglas wrote:

> The mod command went in as commit
> 64e7c440618998fd69eee6ab490b042d12248021
> 
> The traceon/traceoff commands when in as commit
> 23b4ff3aa479c9e3bb23cb6b2d0a97878399784a
> 
> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
> ---
>  Documentation/trace/ftrace.txt |   35 +++++++++++++++++++++++++++++++++++
>  1 files changed, 35 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/trace/ftrace.txt b/Documentation/trace/ftrace.txt
> index 03485bf..64e08d5 100644
> --- a/Documentation/trace/ftrace.txt
> +++ b/Documentation/trace/ftrace.txt
> @@ -155,6 +155,9 @@ of ftrace. Here is a list of some of the key files:
>  	to be traced. Echoing names of functions into this file
>  	will limit the trace to only those functions.
>  
> +	This interface also allows for commands to be used. See the
> +	"Filter commands" section for more details.
> +
>    set_ftrace_notrace:
>  
>  	This has an effect opposite to that of
> @@ -1822,6 +1825,38 @@ this special filter via:
>   echo > set_graph_function
>  
>  
> +Filter commands
> +---------------
> +
> +A few commands are supported by the set_ftrace_filter interface.
> +Trace commands have the following format:
> +
> +<function>:<command>:<parameter>
> +
> +The following commands are supported:
> +
> +- mod
> +  This command enables function filtering per module. The
> +  parameter defines the module. For example, if only the write*
> +  functions in the ext3 module are useful in a trace, echo
> +  'write*:mod:ext3' > set_ftrace_filter. This command interacts

Can we have the echo command all on one line, please?  E.g.:

+  parameter defines the module. For example, if only the write*
+  functions in the ext3 module are useful in a trace, use:
+	echo 'write*:mod:ext3' > set_ftrace_filter
+  This command interacts



> +  with the filter in the same way as filtering based on function
> +  names. Thus, adding more functions in a different module is
> +  accomplished by appending (>>) to the filter file. Remove
> +  specific module functions by prepending '!'
> +  (!writeback*:mod:ext3).
> +
> +- traceon/traceoff
> +  These commands turn tracing on and off when the specified
> +  functions are hit. The parameter determines how many times the
> +  tracing system is turned on and off. If unspecified, there is
> +  no limit. For example, to disable tracing when a schedule bug
> +  is hit the first 5 times, use '__schedule_bug:traceoff:5'.
> +  These commands are cumulative whether or not they are appended
> +  to set_ftrace_filter. To remove a command, prepend it by '!'
> +  and drop the parameter (!__schedule_bug:traceoff).
> +
> +
>  trace_pipe
>  ----------


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2010-04-23 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 16:17 Chase Douglas
2010-04-23 16:55 ` Randy Dunlap [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=20100423095528.668decf8.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=chase.douglas@canonical.com \
    --cc=fweisbec@gmail.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

Powered by JetHome