| commit | 9700798aea993635a449bbc9d7cde7572c160b4a | |
| author | lmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4> | |
| Tue, 26 Apr 2011 16:40:12 +0000 (26 16:40 +0000) | ||
| committer | lmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4> | |
| Tue, 26 Apr 2011 16:40:12 +0000 (26 16:40 +0000) | ||
| tree | 05f44e5d24c58372318f4a7629a01e2aa47ccba8 | treesnapshot (tar.gz zip) |
| parent | bbcb8d959b99af28942939472869413a0deddee7 | commitdiff |
perf profiler: support trace output
As well as reports, one of the other most useful things you can
generate from perf is trace output. Support generating that with
trace=True added to the profiler, e.g.:
job.profilers.add('perf', events=['fs:*'], trace=True)
the output is a raw trace file in the profiling directory.
Signed-off-by: Scott James Remnant <keybuk@chromium.org>
git-svn-id: svn://test.kernel.org/autotest/trunk@5327 592f7852-d20e-0410-864c-8624ca9c26a4
As well as reports, one of the other most useful things you can
generate from perf is trace output. Support generating that with
trace=True added to the profiler, e.g.:
job.profilers.add('perf', events=['fs:*'], trace=True)
the output is a raw trace file in the profiling directory.
Signed-off-by: Scott James Remnant <keybuk@chromium.org>
git-svn-id: svn://test.kernel.org/autotest/trunk@5327 592f7852-d20e-0410-864c-8624ca9c26a4
| client/profilers/perf/perf.py | diffblobblamehistory |