summaryrefslogtreecommitdiffstats
path: root/tools/perf
diff options
context:
space:
mode:
authorSteven Rostedt <rostedt@goodmis.org>2013-11-19 18:29:37 -0500
committerArnaldo Carvalho de Melo <acme@redhat.com>2013-11-27 14:58:34 -0300
commit12e55569a244996a23cb401e8116e5a060b664f0 (patch)
treef899fbffb03df4015638236f26307c5f12e57a87 /tools/perf
parent65661f96d3b32f4b28fef26d21be81d7e173b965 (diff)
downloadop-kernel-dev-12e55569a244996a23cb401e8116e5a060b664f0.zip
op-kernel-dev-12e55569a244996a23cb401e8116e5a060b664f0.tar.gz
tools lib traceevent: Use helper trace-seq in print functions like kernel does
Jiri Olsa reported that his plugin for scsi was chopping off part of the output. Investigating this, I found that Jiri used the same functions as what is in the kernel, which adds the following: trace_seq_putc(p, 0); This adds a '\0' to the output string. The reason this works in the kernel is that the "p" that is passed to the function helper is a temporary trace_seq. But in the libtraceevent library, it's the pointer to the trace_seq used to output. By adding the '\0', it truncates the line and nothing added after that will be printed. We can solve this in two ways. One is to have the helper functions for the library not add the unnecessary '\0'. The other is to change the library to also use a helper trace_seq structure that gets copied to the main trace_seq just like the kernel does. The latter allows the helper functions in the plugins to be the same as the kernel, which is the better solution. Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Reported-by: Jiri Olsa <jolsa@redhat.com> Tested-by: Jiri Olsa <jolsa@redhat.com> Cc: Frederic Weisbecker <fweisbec@gmail.com> Cc: Ingo Molnar <mingo@kernel.org> Cc: Jiri Olsa <jolsa@redhat.com> Cc: Namhyung Kim <namhyung@kernel.org> Link: http://lkml.kernel.org/r/20131119182937.401668e3@gandalf.local.home Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Diffstat (limited to 'tools/perf')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud