Lines Matching refs:py
7 ### app_profiler.py
9 `app_profiler.py` is used to record profiling data for Android applications and native executables.
13 $ ./app_profiler.py -p simpleperf.example.cpp
16 $ ./app_profiler.py -p simpleperf.example.cpp --compile_java_code
19 $ ./app_profiler.py -p simpleperf.example.cpp -a .SleepActivity
22 $ ./app_profiler.py -np surfaceflinger
25 $ ./app_profiler.py --pid 11324
28 $ ./app_profiler.py -cmd \
32 $ ./app_profiler.py -p simpleperf.example.cpp \
36 $ ./app_profiler.py -p simpleperf.example.cpp \
40 $ ./app_profiler.py -p simpleperf.example.cpp -o perf_custom.data
52 $ ./run_simpleperf_on_device.py record --app simpleperf.example.cpp \
57 To make it convenient to use, `app_profiler.py` supports using the `-a` option to start an Activity
61 $ ./app_profiler.py -p simpleperf.example.cpp -a .MainActivity
64 ### api_profiler.py
66 `api_profiler.py` is used to control recording in application code. It does preparation work
71 ### run_simpleperf_without_usb_connection.py
73 `run_simpleperf_without_usb_connection.py` records profiling data while the USB cable isn't
74 connected. Maybe `api_profiler.py` is more suitable, which also don't need USB cable when recording.
78 $ ./run_simpleperf_without_usb_connection.py start -p simpleperf.example.cpp
81 $ ./run_simpleperf_without_usb_connection.py stop
86 ### binary_cache_builder.py
91 `report_html.py` to generate annotated source code and disassembly.
93 By default, `app_profiler.py` builds the binary_cache directory after recording. But we can also
94 build `binary_cache` for existing profiling data files using `binary_cache_builder.py`. It is useful
98 `binary_cache_builder.py` can either pull binaries from an Android device, or find binaries in
103 $ ./binary_cache_builder.py
107 $ ./binary_cache_builder.py -lib path_of_SimpleperfExampleCpp
110 ### run_simpleperf_on_device.py
120 ### report.py
122 report.py is a wrapper of the `report` command on the host. It accepts all options of the `report`
127 $ ./report.py -g
130 $ ./report.py -g --gui
133 ### report_html.py
135 `report_html.py` generates `report.html` based on the profiling data. Then the `report.html` can sh…
143 $ ./report_html.py
146 $ ./report_html.py --add_source_code --source_dirs path_of_SimpleperfExampleCpp
149 $ ./report_html.py --add_disassembly
153 $ ./report_html.py --add_disassembly --binary_filter libgame.so
155 # report_html.py accepts more than one recording data file.
156 $ ./report_html.py -i perf1.data perf2.data
162 $ ./app_profiler.py -p simpleperf.example.cpp
163 $ ./report_html.py --add_source_code --source_dirs path_of_SimpleperfExampleCpp \
204 ### pprof_proto_generator.py
210 $ ./pprof_proto_generator.py
221 ### gecko_profile_generator.py
240 $ ./app_profiler.py -p simpleperf.example.cpp
243 $ ./gecko_profile_generator.py -i perf.data | gzip > gecko-profile.json.gz
248 ### report_sample.py
250 `report_sample.py` converts a profiling data file into the `perf script` text format output by
259 but prefer using `gecko_profile_generator.py`.
264 $ ./app_profiler.py <args>
267 $ ./report_sample.py --symfs binary_cache >out.perf
274 ### stackcollapse.py
276 `stackcollapse.py` converts a profiling data file (`perf.data`) to [Brendan
299 $ ./app_profiler.py <args>
302 $ ./stackcollapse.py --kernel --jit | gzip > profile.folded.gz
311 ## simpleperf_report_lib.py
313 `simpleperf_report_lib.py` is a Python library used to parse profiling data files generated by the
321 Examples of using `simpleperf_report_lib.py` are in `report_sample.py`, `report_html.py`,
322 `pprof_proto_generator.py` and `inferno/inferno.py`.