linux-toradex.git/kernel/trace/ftrace.c, branch v2.6.27.23

stop_machine: fix up ftrace.c

2008-07-28T02:16:31+00:00

Simple conversion.

Signed-off-by: Rusty Russell 
Cc: Abhishek Sagar 
Cc: Ingo Molnar 
Cc: Steven Rostedt

ftrace: build fix for ftraced_suspend

2008-07-11T14:46:50+00:00

fix:

 kernel/trace/ftrace.c:1615: error: 'ftraced_suspend' undeclared (first use in this function)
 kernel/trace/ftrace.c:1615: error: (Each undeclared identifier is reported only once
 kernel/trace/ftrace.c:1615: error: for each function it appears in.)

Signed-off-by: Ingo Molnar

ftrace: add ftrace_kill_atomic

2008-07-11T13:49:21+00:00

It has been suggested that I add a way to disable the function tracer
on an oops. This code adds a ftrace_kill_atomic. It is not meant to be
used in normal situations. It will disable the ftrace tracer, but will
not perform the nice shutdown that requires scheduling.

Signed-off-by: Steven Rostedt 
Cc: Steven Rostedt 
Cc: Peter Zijlstra 
Cc: Andrew Morton 
Signed-off-by: Ingo Molnar

ftrace: prevent ftrace modifications while being kprobe'd, v2

2008-07-03T12:46:24+00:00

add two missing chunks for ftrace+kprobe.

Signed-off-by: Abhishek Sagar 
Cc: Steven Rostedt 
Signed-off-by: Ingo Molnar

ftrace: avoid modifying kprobe'd records

2008-06-23T20:10:59+00:00

Avoid modifying the mcount call-site if there is a kprobe installed on it.
These records are not marked as failed however. This allowed the filter
rules on them to remain up-to-date. Whenever the kprobe on the corresponding
record is removed, the record gets updated as normal.

Signed-off-by: Abhishek Sagar 
Cc: Steven Rostedt 
Signed-off-by: Ingo Molnar

ftrace: freeze kprobe'd records

2008-06-23T20:10:58+00:00

Let records identified as being kprobe'd be marked as "frozen". The trouble
with records which have a kprobe installed on their mcount call-site is
that they don't get updated. So if such a function which is currently being
traced gets its tracing disabled due to a new filter rule (or because it
was added to the notrace list) then it won't be updated and continue being
traced. This patch allows scanning of all frozen records during tracing to
check if they should be traced.

Signed-off-by: Abhishek Sagar 
Cc: Steven Rostedt 
Signed-off-by: Ingo Molnar

ftrace: store mcount address in rec->ip

2008-06-23T20:10:56+00:00

Record the address of the mcount call-site. Currently all archs except sparc64
record the address of the instruction following the mcount call-site. Some
general cleanups are entailed. Storing mcount addresses in rec->ip enables
looking them up in the kprobe hash table later on to check if they're kprobe'd.

Signed-off-by: Abhishek Sagar 
Cc: davem@davemloft.net
Cc: Steven Rostedt 
Signed-off-by: Ingo Molnar

namespacecheck: fixes

2008-06-16T12:44:13+00:00

Signed-off-by: Ingo Molnar

ftrace: fix "notrace" filtering priority

2008-06-14T06:32:29+00:00

This is a fix to give notrace filter rules priority over "set_ftrace_filter"
rules.

This fix ensures that functions which are set to be filtered and are
concurrently marked as "notrace" don't get recorded. As of now, if
a record is marked as FTRACE_FL_FILTER and is enabled, then the notrace
flag is not checked. Tested on x86-32.

Signed-off-by: Abhishek Sagar 
Signed-off-by: Ingo Molnar

ftrace: prevent freeing of all failed updates

2008-06-10T09:59:05+00:00

Steven Rostedt wrote:
> If we unload a module and reload it, will it ever get converted again?

The intent was always to filter core kernel functions to prevent their freeing.
Here's a fix which should allow re-recording of module call-sites.

Signed-off-by: Ingo Molnar