Lines Matching refs:how

7   - [How simpleperf works](#how-simpleperf-works)
13     - [Decide how long to stat](#decide-how-long-to-stat)
22     - [Decide how long to record](#decide-how-long-to-record)
37 several hardware counters, counting events like how many cpu cycles have happened, how many
38 instructions have executed, or how many cache misses have happened.
46 The stat command gives a summary of how many events have happened in the profiled processes in a
47 time period. Here’s how it works:
52 The record command records samples of the profiled processes in a time period. Here’s how it works:
122 we can select which events to use, which processes/threads to monitor, how long to monitor and the
221 ### Decide how long to stat
223 When monitoring existing threads, we can use --duration to decide how long to monitor. When
239 If you want to write a script to control how long to monitor, you can send one of SIGINT, SIGTERM,
295 option is used, stat cmd outputs an event count for each core. It can be used to see how events
332 what frequency to dump samples, how long to monitor, and where to store samples.
402 ### Decide how long to record
404 The way to decide how long to monitor in record command is similar to that in the stat command.
418 If you want to write a script to control how long to monitor, you can send one of SIGINT, SIGTERM,
453 A call graph shows how a function calls other functions, and a reversed call graph shows how
540 By passing options, we can decide how to filter out uninteresting samples, how to group samples
619 The report command uses --sort to decide how to group sample entries.