Lines Matching refs:report
26 - [The report command](#the-report-command)
31 - [Report call graphs](#report-call-graphs)
44 Simpleperf has three main commands: stat, record and report.
60 The report command reads perf.data and any shared libraries used by the profiled processes,
61 and outputs a report showing where the time was spent.
74 The report command: reports profiling data in perf.data.
75 The report-sample command: reports each sample in perf.data, used for supporting integration of
91 Below describes the most frequently used commands, which are list, stat, record and report.
455 report it.
490 with other events or multiple events doesn't make much sense and makes the report confusing.
533 ## The report command
535 The report command is used to report profiling data generated by the record command. The report
536 contains a table of sample entries. Each sample entry is a row in the report. The report command
553 $ simpleperf report --dsos /data/app/com.example.sudogame-2/lib/arm64/libsudo-game-jni.so \
570 By default, the report command reads profiling data from perf.data in the current directory.
574 $ simpleperf report -i data/perf2.data
579 To report function symbols, simpleperf needs to read executable binaries used by the monitored
587 $ simpleperf report
591 $ simpleperf report --symfs /debug_dir
595 $ simpleperf report --symfs $ANDROID_PRODUCT_OUT/symbols
600 When reporting, it happens that not all records are of interest. The report command supports four
605 $ simpleperf report --comms sudogame
608 $ simpleperf report --pids 7394,7395
611 $ simpleperf report --tids 7394,7395
614 $ simpleperf report --dsos /data/app/com.example.sudogame-2/lib/arm64/libsudo-game-jni.so
619 The report command uses --sort to decide how to group sample entries.
624 $ simpleperf report --sort pid
628 $ simpleperf report --sort tid,comm
632 $ simpleperf report --sort dso,symbol
636 $ simpleperf report
641 To report a call graph, please make sure the profiling data is recorded with call graphs,
645 $ simpleperf report -g