diff options
author | Arnaldo Carvalho de Melo <acme@redhat.com> | 2010-03-05 18:23:50 -0300 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2010-03-05 21:12:08 -0500 |
commit | 1acaa1b2d9b5904c9cce06122990a2d71046ce16 (patch) | |
tree | 76e4d061aa4c666c89f581e438b105bd69ee27df /kernel/trace/trace_functions_graph.c | |
parent | a094fe04c751698a18c3a0d376a3bdb117f1e0d8 (diff) | |
download | op-kernel-dev-1acaa1b2d9b5904c9cce06122990a2d71046ce16.zip op-kernel-dev-1acaa1b2d9b5904c9cce06122990a2d71046ce16.tar.gz |
tracing: Update the comm field in the right variable in update_max_tr
The latency output showed:
# | task: -3 (uid:0 nice:0 policy:1 rt_prio:99)
The comm is missing in the "task:" and it looks like a minus 3 is
the output. The correct display should be:
# | task: migration/0-3 (uid:0 nice:0 policy:1 rt_prio:99)
The problem is that the comm is being stored in the wrong data
structure. The max_tr.data[cpu] is what stores the comm, not the
tr->data[cpu].
Before this patch the max_tr.data[cpu]->comm was zeroed and the /debug/trace
ended up showing just the '-' sign followed by the pid.
Also remove a needless initialization of max_data.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <1267824230-23861-1-git-send-email-acme@infradead.org>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace_functions_graph.c')
0 files changed, 0 insertions, 0 deletions