Home
last modified time | relevance | path

Searched refs:perf (Results 1 – 25 of 29) sorted by relevance

12

/system/extras/simpleperf/
Drecord_lib_test.cpp40 std::unique_ptr<PerfEventSet> perf(PerfEventSet::CreateInstance( in TEST() local
42 ASSERT_TRUE(perf); in TEST()
43 ASSERT_TRUE(perf->AddEvent("cpu-cycles")); in TEST()
44 ASSERT_TRUE(perf->AddEvent("cpu-cycles:u")); in TEST()
45 ASSERT_TRUE(perf->AddEvent("cpu-cycles:k")); in TEST()
46 ASSERT_TRUE(perf->MonitorCurrentProcess()); in TEST()
47 ASSERT_TRUE(perf->StartCounters()); in TEST()
49 ASSERT_TRUE(perf->StopCounters()); in TEST()
51 ASSERT_TRUE(perf->ReadCounters(&counters)); in TEST()
66 std::unique_ptr<PerfEventSet> perf(PerfEventSet::CreateInstance( in TEST() local
[all …]
Dreport_sample.proto21 // By default, it is perf clock used in kernel.
/system/core/storaged/
Dstoraged_diskstats.cpp40 void log_debug_disk_perf(struct disk_perf* perf, const char* type) { in log_debug_disk_perf() argument
42 if (perf == NULL || perf->is_zero()) return; in log_debug_disk_perf()
44 LOG(INFO) << "disk_perf " << type << " rd: " << perf->read_perf << " kbps, " << perf->read_ios in log_debug_disk_perf()
46 << " wr: " << perf->write_perf << " kbps, " << perf->write_ios << " iops" in log_debug_disk_perf()
47 << " q: " << perf->queue; in log_debug_disk_perf()
50 void log_debug_disk_perf(struct disk_perf* perf, const char* type) {} in log_debug_disk_perf() argument
161 struct disk_perf perf = {}; in get_disk_perf() local
166 perf.read_perf = ((unsigned long long)SECTOR_SIZE * in get_disk_perf()
169 perf.read_ios = ((unsigned long long)SEC_TO_MSEC * in get_disk_perf()
175 perf.write_perf = ((unsigned long long)SECTOR_SIZE * in get_disk_perf()
[all …]
Dstoraged.cpp279 int perf = benchmark_size * 1000000LLU / benchmark_time_ns; in flush_proto_data() local
280 storage_info->update_perf_history(perf, system_clock::now()); in flush_proto_data()
/system/extras/zram-perf/
DAndroid.bp2 name: "zram-perf",
11 srcs: ["zram-perf.cpp"],
/system/extras/simpleperf/doc/
Dscripts_reference.md53 # Save profiling data in a custom file (like perf_custom.data) instead of perf.data.
68 -g --duration 1 -o /data/local/tmp/perf.data
98 # It may take a while to stop recording. After that, the profiling data is collected in perf.data
118 # Generate binary_cache for perf.data, by pulling binaries from the device.
153 # Generate chart statistics, sample table and flamegraphs, based on perf.data.
203 # Generate flamegraph based on perf.data.
205 $ ./inferno.sh -sc --record_file perf.data
216 # Convert perf.data in the current directory to pprof.proto format.
233 # Convert perf.data in the current directory to a format used by FlameGraph.
234 $ python report_sample.py --symfs binary_cache >out.perf
[all …]
Dandroid_application_profiling.md142 # Cd to the directory of simpleperf scripts. Record perf.data.
152 This will collect profiling data in perf.data in the current directory, and related native
159 # Report perf.data in stdio interface.
177 # Report perf.data in html interface.
242 $ python report_sample.py --symfs binary_cache >out.perf
243 $ FlameGraph/stackcollapse-perf.pl out.perf >out.folded
249 simpleperf report-sample command can convert perf.data into protobuf format accepted by
254 $ simpleperf report-sample --protobuf --show-callchain -i perf.data -o perf.trace
255 # Then open perf.trace in Android Studio to show it.
Dexecutable_commands_reference.md40 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
[all …]
Dandroid_platform_profiling.md35 # Doing recording with app_profiler.py or simpleperf on device, and generates perf.data on host.
64 + " -o /data/perf.data --duration 30 --log-to-android-buffer --log verbose");
73 When monitoring instruction and cache related perf events (in hw/cache/raw/pmu category of list cmd…
DREADME.md35 The simpleperf executable works similar to linux-tools-perf, but has some specific features for
164 The simpleperf record command collects symbols on device in perf.data. But if the native libraries
169 # Collect binaries needed by perf.data in binary_cache/.
216 a. Generate perf.data and pull it on host.
219 `binary_cache_builder.py -i perf.data -lib <dir_of_lib_with_debug_info>`.
225 a. Generate perf.data and binary_cache as above.
Dinferno.md46 dumps dumped to a file `perf.data`. This file is pulled from the Android device
/system/core/storaged/include/
Dstoraged_diskstats.h169 void add(struct disk_perf* perf);
170 void evict(struct disk_perf* perf);
171 bool detect(struct disk_perf* perf);
/system/extras/tests/workloads/
Dpwrsummary.sh65 …rintf "%s,%s,%s,%s,%s,%s,%s,%s,%s\n" " " build min ave max net-mA@${voltage}v base-mW net-mW perf/W
67 …s %12.12s %12.12s %12.12s %12.12s\n" " " build min ave max net-mA@${voltage}v base-mW net-mW perf/W
/system/core/storaged/tests/
Dstoraged_test.cpp184 struct disk_perf disk_perf_multiply(struct disk_perf perf, double mul) { in disk_perf_multiply() argument
186 retval.read_perf = (double)perf.read_perf * mul; in disk_perf_multiply()
187 retval.read_ios = (double)perf.read_ios * mul; in disk_perf_multiply()
188 retval.write_perf = (double)perf.write_perf * mul; in disk_perf_multiply()
189 retval.write_ios = (double)perf.write_ios * mul; in disk_perf_multiply()
190 retval.queue = (double)perf.queue * mul; in disk_perf_multiply()
265 struct disk_perf perf = disk_perf_multiply(norm_perf, rand(gen)); in TEST() local
267 dsm_detect.add(&perf); in TEST()
268 dsm_detect.mBuffer.push(perf); in TEST()
/system/sepolicy/prebuilts/api/26.0/public/
Dperfprofd.te1 # perfprofd - perf profile collection daemon
36 # simpleperf uses ioctl() to turn on kernel perf events measurements
/system/sepolicy/prebuilts/api/27.0/public/
Dperfprofd.te1 # perfprofd - perf profile collection daemon
36 # simpleperf uses ioctl() to turn on kernel perf events measurements
/system/extras/simpleperf/demo/
DREADME.md65 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
97 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
129 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
/system/sepolicy/prebuilts/api/28.0/private/
Datrace.te39 # atrace is generally invoked as a standalone binary from shell or perf
/system/sepolicy/prebuilts/api/29.0/public/
Dperfprofd.te1 # perfprofd - perf profile collection daemon
59 # simpleperf uses ioctl() to turn on kernel perf events measurements
/system/sepolicy/prebuilts/api/28.0/public/
Dperfprofd.te1 # perfprofd - perf profile collection daemon
59 # simpleperf uses ioctl() to turn on kernel perf events measurements
/system/sepolicy/prebuilts/api/29.0/private/
Datrace.te53 # atrace is generally invoked as a standalone binary from shell or perf
/system/sepolicy/prebuilts/api/30.0/private/
Dtraced_perf.te2 # See go/perfetto-perf-android.
Datrace.te73 # atrace is generally invoked as a standalone binary from shell or perf
/system/sepolicy/private/
Dtraced_perf.te2 # See go/perfetto-perf-android.
Datrace.te73 # atrace is generally invoked as a standalone binary from shell or perf

12