mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
Subject: Re: [for-next][PATCH 9/9] tracing: Update debugfs README file
Date: Mon, 18 Mar 2013 09:18:50 -0400	[thread overview]
Message-ID: <1363612730.25967.138.camel@gandalf.local.home> (raw)
In-Reply-To: <87hak9jewo.fsf@sejong.aot.lge.com>

On Mon, 2013-03-18 at 17:22 +0900, Namhyung Kim wrote:

> > +	"             example: echo do_fault:traceoff > set_ftrace_filter\n"
> > +	"                      echo do_trap:traceoff:3 > set_ftrace_filter\n"
> > +	"             The first one will disable tracing everytime do_fault is hit\n"
> > +	"             The second will disable tracing at most 3 times whne do_trap is hit\n"
> 
> s/whne/when/
> 
> It's slightly confusing for me to read the "at most" part.  Did you mean
> it by "The second will disable tracing after do_trace is hit 3 times"?

Yeah, I wrote this on little sleep. I'll revise it a little. Thanks!

-- Steve


> 
> > +	"             To remove trigger without count:\n"
> > +	"               echo '!<function>:<trigger> > set_ftrace_filter\n"
> > +	"             To remove trigger with a count:\n"
> > +	"               echo '!<function>:<trigger>:0 > set_ftrace_filter\n"
> > +	"  set_ftrace_notrace\t- echo function name in here to never trace.\n"
> > +	"            accepts: func_full_name, *func_end, func_begin*, *func_middle*\n"
> > +	"            modules: Can select a group via module command :mod:\n"
> > +	"            Does not accept triggers\n"
> > +#endif /* CONFIG_DYNAMIC_FTRACE */



      parent reply	other threads:[~2013-03-18 13:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16  3:24 [for-next][PATCH 0/9] tracing: ring-buffer selftest, cleanups, ftrace_dump() fix and document Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 1/9] ring-buffer: Add ring buffer startup selftest Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 2/9] tracing: Use pr_warn_once instead of open coded implementation Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 3/9] tracing: Use TRACE_MAX_PRINT instead of constant Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 4/9] tracing: Move find_event_field() into trace_events.c Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 5/9] tracing: Convert trace_destroy_fields() to static Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 6/9] tracing: Fix comment about prefix in arch_syscall_match_sym_name() Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 7/9] tracing: Rename trace_event_mutex to trace_event_sem Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 8/9] tracing: Fix ftrace_dump() Steven Rostedt
2013-03-16  3:24 ` [for-next][PATCH 9/9] tracing: Update debugfs README file Steven Rostedt
2013-03-18  8:22   ` Namhyung Kim
2013-03-18  9:03     ` Keun-O Park
2013-03-18 13:19       ` Steven Rostedt
2013-03-21  2:02       ` Steven Rostedt
2013-03-18 13:18     ` Steven Rostedt [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=1363612730.25967.138.camel@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=jovi.zhangwei@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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

all inboxes | Powered by JetHome®