trace/coresight/coresight-perf.rst

4 CoreSight - Perf
10 Perf is able to locally access CoreSight trace data and store it to the
11 output perf data files. This data can then be later decoded to give the
13 can log such data with a perf record command like::
15    perf record -e cs_etm//u testbinary
18 a perf.data trace file. That file would have AUX sections if CoreSight
22    perf report --stdio --dump -i perf.data
43 To compile perf with CoreSight support in the tools/perf directory do::
53 For complete information on building perf with CoreSight support and
81 Perf test - Verify kernel and userspace perf CoreSight work
84 When you run perf test, it will do a lot of self tests. Some of those
86 generally would run perf test from the tools/perf directory in the
87 kernel tree. Some tests will check some internal perf support like:
92 Some others will actually use perf record and some test binaries that
102 These perf record tests will not run if the tool binaries do not exist
104 CoreSight support in hardware then either do not build perf with
109 directory (e.g. tools/perf) and will be named stats-\*.csv like:
116 the perf data output counting some numbers of certain encodings (a
121 that the amount of data collected can vary a lot per run of perf test.
122 If you wish to see how this changes over time, simply run perf test
133 in processing the perf data file and dumping contents to then examine what
137 PERF_TEST_CORESIGHT_STATDIR environment variable before running perf
141    perf test
143 They will also store resulting perf output data in the current
146    perf-asm_pure_loop-out.data
147    perf-memcpy_thread-16k_10.data
150 You can alter where the perf data files are stored by setting the
154    perf test