diff options
| author | Miao Xie <miaox@cn.fujitsu.com> | 2013-12-16 15:20:01 +0800 | 
|---|---|---|
| committer | Steven Rostedt <rostedt@goodmis.org> | 2013-12-16 10:53:46 -0500 | 
| commit | c4602c1c818bd6626178d6d3fcc152d9f2f48ac0 (patch) | |
| tree | f09af73ac1a12cea420b02ca5970c769ce479e29 /drivers/net/wireless/hostap/hostap_main.c | |
| parent | 3ccb01239201af06a07482ec686b14cd148102a5 (diff) | |
ftrace: Initialize the ftrace profiler for each possible cpu
Ftrace currently initializes only the online CPUs. This implementation has
two problems:
- If we online a CPU after we enable the function profile, and then run the
  test, we will lose the trace information on that CPU.
  Steps to reproduce:
  # echo 0 > /sys/devices/system/cpu/cpu1/online
  # cd <debugfs>/tracing/
  # echo <some function name> >> set_ftrace_filter
  # echo 1 > function_profile_enabled
  # echo 1 > /sys/devices/system/cpu/cpu1/online
  # run test
- If we offline a CPU before we enable the function profile, we will not clear
  the trace information when we enable the function profile. It will trouble
  the users.
  Steps to reproduce:
  # cd <debugfs>/tracing/
  # echo <some function name> >> set_ftrace_filter
  # echo 1 > function_profile_enabled
  # run test
  # cat trace_stat/function*
  # echo 0 > /sys/devices/system/cpu/cpu1/online
  # echo 0 > function_profile_enabled
  # echo 1 > function_profile_enabled
  # cat trace_stat/function*
  # run test
  # cat trace_stat/function*
So it is better that we initialize the ftrace profiler for each possible cpu
every time we enable the function profile instead of just the online ones.
Link: http://lkml.kernel.org/r/1387178401-10619-1-git-send-email-miaox@cn.fujitsu.com
Cc: stable@vger.kernel.org # 2.6.31+
Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'drivers/net/wireless/hostap/hostap_main.c')
0 files changed, 0 insertions, 0 deletions
