tracing/stack_trace: Skip 4 instead of 3 when using ftrace_ops_list_func
authorJiaxing Wang <wangjiaxing@insigma.com.cn>
Sun, 20 Apr 2014 15:10:43 +0000 (23:10 +0800)
committerSteven Rostedt <rostedt@goodmis.org>
Thu, 24 Apr 2014 17:36:03 +0000 (13:36 -0400)
commit7eea4fce0246fe3a15ad7f3bb8d0a56d1f9440e6
tree48f2171d7626e8a09a962cc68b1accfc0c59f2d7
parentad1438a076e275b70d1a04de1364bc483e5a81db
tracing/stack_trace: Skip 4 instead of 3 when using ftrace_ops_list_func

When using ftrace_ops_list_func, we should skip 4 instead of 3,
to avoid ftrace_call+0x5/0xb appearing in the stack trace:

        Depth    Size   Location    (110 entries)
        -----    ----   --------
  0)     2956       0   update_curr+0xe/0x1e0
  1)     2956      68   ftrace_call+0x5/0xb
  2)     2888      92   enqueue_entity+0x53/0xe80
  3)     2796      80   enqueue_task_fair+0x47/0x7e0
  4)     2716      28   enqueue_task+0x45/0x70
  5)     2688      12   activate_task+0x22/0x30

Add a function using_ftrace_ops_list_func() to test for this while keeping
ftrace_ops_list_func to remain static.

Link: http://lkml.kernel.org/p/1398006644-5935-2-git-send-email-wangjiaxing@insigma.com.cn
Signed-off-by: Jiaxing Wang <wangjiaxing@insigma.com.cn>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
kernel/trace/ftrace.c
kernel/trace/trace.h
kernel/trace/trace_stack.c