linux-kernel - Re: [12/19] ftrace: function tracer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 10 Feb 2008 17:53:53 +0800
From:	Eugene Teo <eugeneteo@...nel.sg>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@....com.au>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [12/19] ftrace: function tracer

<quote sender="Ingo Molnar">
> From: Steven Rostedt <srostedt@...hat.com>
> 
> This is a simple trace that uses the ftrace infrastructure. It is
> designed to be fast and small, and easy to use. It is useful to
> record things that happen over a very short period of time, and
> not to analyze the system in general.
> 
>  Updates:
> 
>   available_tracers
>      "function" is added to this file.

$ cat available_tracers 
wakeup irqsoff ftrace sched_switch none
               ^^^^^^

I believe "function" refers to "ftrace"?

[...]
>  echo "symonly" > /debugfs/tracing/iter_ctrl
> 
> tracer:
> [   81.479913] CPU 0: bash:3154 register_ftrace_function+0x5f/0x66 <-- _spin_unlock_irqrestore+0xe/0x5a
> [   81.479913] CPU 0: bash:3154 _spin_unlock_irqrestore+0x3e/0x5a <-- sub_preempt_count+0xc/0x7a
> [   81.479913] CPU 0: bash:3154 sub_preempt_count+0x30/0x7a <-- in_lock_functions+0x9/0x24
> [   81.479914] CPU 0: bash:3154 vfs_write+0x11d/0x155 <-- dnotify_parent+0x12/0x78
> [   81.479914] CPU 0: bash:3154 dnotify_parent+0x2d/0x78 <-- _spin_lock+0xe/0x70
> [   81.479914] CPU 0: bash:3154 _spin_lock+0x1b/0x70 <-- add_preempt_count+0xe/0x77
> [   81.479914] CPU 0: bash:3154 add_preempt_count+0x3e/0x77 <-- in_lock_functions+0x9/0x24

I can't seem to echo "symonly" to iter_ctrl.

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?

Thanks,
Eugene
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/