From: Steven Rostedt <rostedt@goodmis.org>
To: Rajesh Bhagat <rajesh.lnx@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ftrace: fix dynamic ftrace filter reset issue
Date: Sat, 24 Mar 2012 09:55:05 -0400 [thread overview]
Message-ID: <1332597305.12799.2.camel@acer.local.home> (raw)
In-Reply-To: <CA+jqyFAzpTs+JeemD7wpSgW0hmECMSPMsaZtQ7zLgn+ebXSJFQ@mail.gmail.com>
On Sat, 2012-03-24 at 09:47 +0530, Rajesh Bhagat wrote:
> Hi Steven,
>
> Thanks for the reply.
>
> I was wondering, why would a user reset the trace __explicitly__
> without even using it.
> That is why i created a patch for it.
>
> >> /debug/tracing # echo function > current_tracer
^
|
user starts using tracer
> >> /debug/tracing # cat trace <------ Not performed
> >> /debug/tracing # echo schedule > set_ftrace_filter
> >> /debug/tracing # echo function > current_trace
> >> /debug/tracing # cat trace <------- Only this is performed
Why the first "echo function"? That means you just started using the
tracer. You can (and should) do:
# echo schedule > set_ftrace_filter
# echo function > current_tracer
This IIRC is the documented way of using it.
That said, I may consider taking the patch, as another way of resetting
the tracer. I have to see what workflows it will affect first.
-- Steve
next prev parent reply other threads:[~2012-03-24 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 5:52 Rajesh Bhagat
2012-03-23 19:36 ` Steven Rostedt
2012-03-24 4:17 ` Rajesh Bhagat
2012-03-24 4:53 ` Rajesh Bhagat
2012-03-24 13:55 ` Steven Rostedt [this message]
2012-03-25 18:11 ` Rajesh Bhagat
2012-03-26 17:45 ` Steven Rostedt
2012-03-27 3:51 ` Rajesh Bhagat
2012-03-26 17:13 ` Steven Rostedt
2012-03-26 18:19 ` Rajesh Bhagat
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=1332597305.12799.2.camel@acer.local.home \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rajesh.lnx@gmail.com \
/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®