lkml.org 
[lkml]   [2012]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC PATCH -tip 0/9]ftrace, kprobes: Ftrace-based kprobe optimization
From
Date
On Wed, 2012-05-30 at 15:59 +0900, Masami Hiramatsu wrote:

> Hmm, I'm not so sure how the notrace and filter works.
> What happens if I set a foo function-entry on filter
> and keep notrace empty?
> - only foo's nop is replaced with call?
> - or all functions including foo is traced?

From Documentation/trace/ftrace.txt:

"If a function exists in both set_ftrace_filter
and set_ftrace_notrace, the function will _not_ be traced."

The filters work exactly the same. If notrace always take precedence
over filter. If you have foo and bar in filter, and put foo in notrace,
then only bar is traced.

"filter" means "limit tracing only to these functions"
"notrace" means "do not trace this function"

Think of 'filter' as a way of making the 'available_filter_functions'
smaller. It filters the list. But 'notrace' is just like adding a
'notrace' tag. It stops it from being traced regardless.

-- Steve





\
 
 \ /
  Last update: 2012-05-30 14:21    [W:0.134 / U:0.912 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site