Lines Matching refs:how

26     - [How simpleperf works](#how-simpleperf-works)
32         - [Decide how long to stat](#decide-how-long-to-stat)
39         - [Decide how long to record](#decide-how-long-to-record)
64     - [How to solve missing symbols in report](#how-to-solve-missing-symbols-in-report)
151 This section shows how to profile an Android application.
293 symbols in the report, check [here](#how-to-solve-missing-symbols-in-report).
452 several hardware counters, counting events like how many cpu cycles have happened, how many
453 instructions have executed, or how many cache misses have happened.
461 The stat command gives a summary of how many events have happened in the profiled processes in a
462 time period. Here’s how it works:
467 The record command records samples of the profiled processes in a time period. Here’s how it works:
537 we can select which events to use, which processes/threads to monitor, how long to monitor and the
636 #### Decide how long to stat
638 When monitoring existing threads, we can use --duration to decide how long to monitor. When
654 If you want to write a script to control how long to monitor, you can send one of SIGINT, SIGTERM,
691 what frequency to dump samples, how long to monitor, and where to store samples.
761 #### Decide how long to record
763 The way to decide how long to monitor in record command is similar to that in the stat command.
777 If you want to write a script to control how long to monitor, you can send one of SIGINT, SIGTERM,
813 A call graph shows how a function calls other functions, and a reversed call graph shows how
898 By passing options, we can decide how to filter out uninteresting samples, how to group samples
977 The report command uses --sort to decide how to group sample entries.