Lines Matching refs:cycles
37 several hardware counters, counting events like how many cpu cycles have happened, how many
104 cpu-cycles
115 events. For example, raw-cpu-cycles is wrapped into cpu-cycles, raw-instruction-retired is wrapped
126 # Stat using default events (cpu-cycles,instructions,...), and monitor process 7394 for 10 seconds.
130 1,320,496,145 cpu-cycles # 0.131736 GHz (100%)
131 510,426,028 instructions # 2.587047 cycles per instruction (100%)
145 # Stat event cpu-cycles.
146 $ simpleperf stat -e cpu-cycles -p 11904 --duration 10
310 7 56,552,838 cpu-cycles # (60%)
311 3 25,958,605 cpu-cycles # (20%)
312 0 22,822,698 cpu-cycles # (15%)
313 1 6,661,495 cpu-cycles # (5%)
314 4 1,519,093 cpu-cycles # (0%)
322 $ su 0 simpleperf stat -e cpu-cycles -a --per-thread --per-core --duration 1
335 # Record on process 7394 for 10 seconds, using default event (cpu-cycles), using default sample
343 By default, the cpu-cycles event is used to evaluate consumed cpu cycles. But we can also use other
489 trace-offcpu only works with recording one of events: cpu-cycles, cpu-clock, task-clock. Using it
546 events. As the perf event is cpu-cycles, the overhead is the percentage of CPU cycles used in each
557 Event: cpu-cycles (type 0, config 0)