Lines Matching refs:perf

40 The Linux kernel wraps these hardware counters into hardware perf events. In addition, the Linux
58    perf.data.
60 The report command reads perf.data and any shared libraries used by the profiled processes,
69 The dump command: dumps content in perf.data, used for debugging simpleperf.
73 The record command: profiles processes and stores profiling data in perf.data.
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
244 When monitoring perf counters, we can also use --interval to decide the print interval.
266 # Open the collected new.html in browser and perf counters will be shown up.
297 When stating non-system wide with `--per-core` option, simpleperf creates a perf event for each
298 monitored thread on each core. When a thread is in running state, perf events on all cores are
299 enabled, but only the perf event on the core running the thread is in running state. So the
336 # frequency (4000 samples per second), writing records to perf.data.
423 By default, simpleperf stores profiling data in perf.data in the current directory. But the path
480 so we know the callstack of a thread when it is scheduled out. And when reporting a perf.data
546 events. As the perf event is cpu-cycles, the overhead is the percentage of CPU cycles used in each
550 # Reports perf.data, using only records sampled in libsudo-game-jni.so, grouping records using
570 By default, the report command reads profiling data from perf.data in the current directory.