summaryrefslogtreecommitdiff
path: root/fs/logfs
diff options
context:
space:
mode:
authorArjan van de Ven <arjan@linux.intel.com>2010-08-18 15:33:13 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2010-08-26 16:46:32 -0700
commitbdf6e8eb218794850dfff2e2858590fda91e7f36 (patch)
tree07239e675067276b0e185a0f0916a3860ebec482 /fs/logfs
parentf5d76aba51998b28810ae026a30577bd8d2abae5 (diff)
tracing: Fix timer tracing
commit ede1b4290781ae82ccf0f2ecc6dada8d3dd35779 upstream. PowerTOP would like to be able to trace timers. Unfortunately, the current timer tracing is not very useful: the actual timer function is not recorded in the trace at the start of timer execution. Although this is recorded for timer "start" time (when it gets armed), this is not useful; most timers get started early, and a tracer like PowerTOP will never see this event, but will only see the actual running of the timer. This patch just adds the function to the timer tracing; I've verified with PowerTOP that now it can get useful information about timers. Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Cc: xiaoguangrong@cn.fujitsu.com Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Frederic Weisbecker <fweisbec@gmail.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> LKML-Reference: <4C6C5FA9.3000405@linux.intel.com> Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs/logfs')
0 files changed, 0 insertions, 0 deletions