From: Ingo Molnar <mingo@elte.hu>
To: Eugene Teo <eugeneteo@kernel.sg>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@zip.com.au>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [12/19] ftrace: function tracer
Date: Sun, 10 Feb 2008 16:19:11 +0100 [thread overview]
Message-ID: <20080210151911.GA28201@elte.hu> (raw)
In-Reply-To: <20080210095353.GA8451@kernel.sg>
* Eugene Teo <eugeneteo@kernel.sg> wrote:
> kerndev: /sys/kernel/debug/tracing$ cat current_tracer
> ftrace
> kerndev: /sys/kernel/debug/tracing$ cat tracing_enabled
> 1
> kerndev: /sys/kernel/debug/tracing$ cat iter_ctrl
> noprint-parent nosym-offset nosym-addr noverbose
> kerndev: /sys/kernel/debug/tracing$ echo symonly > iter_ctrl
> kerndev: /sys/kernel/debug/tracing$ cat iter_ctrl
> noprint-parent nosym-offset nosym-addr noverbose
>
> How did you get the above output?
the logic is this: the iter_ctl flags are either "noprint-parent" or
"print-parent". You can toggle it by writing the opposite into that
file. The "symonly" was an older flag - we'll update documentation with
that.
so for example to print out the symbol addresses in hexa too, do:
echo sym-addr > iter_ctrl
to turn that aspect of trace display off, do:
echo nosym-addr > iter_ctrl
we'll gravitate the defaults to something that is OK to most people, but
certain purposes need more (or less) information, so the various toggles
are still quite useful. (Previously we kept all the toggles as separate
switches, but that was more confusing - now it's concentrated into a
single control.)
Ingo
prev parent reply other threads:[~2008-02-10 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 7:20 [12/19] ftrace: function tracer Ingo Molnar
2008-02-10 9:53 ` Eugene Teo
2008-02-10 15:19 ` Ingo Molnar [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=20080210151911.GA28201@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@zip.com.au \
--cc=eugeneteo@kernel.sg \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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