Lines Matching full:perf

33 // JitLogger supports two approaches of perf profiling.
35 // (1) perf-map:
36 // The perf-map mechanism generates perf-PID.map file,
37 // which provides simple "address, size, method_name" information to perf,
38 // and allows perf to map samples in jit-code-cache to jitted method symbols.
41 // $ perf record dalvikvm -Xcompiler-option --generate-debug-info -cp <classpath> Test
42 // $ perf report
44 // - Make sure that the perf-PID.map file is available for 'perf report' tool to access,
48 // (2) perf-inject:
49 // The perf-inject mechansim generates jit-PID.dump file,
51 // It allows perf or other profiling tools to do advanced analysis on jitted code,
55 // $ perf record -k mono dalvikvm -Xcompiler-option --generate-debug-info -cp <classpath> Test
56 // $ perf inject -j -i perf.data -o perf.data.jitted
57 // $ perf report -i perf.data.jitted
58 // $ perf annotate -i perf.data.jitted
61 // - The 'perf record -k mono' option requires 4.1 (or higher) Linux kernel.
62 // - The 'perf inject' (generating jit ELF files feature) requires perf 4.6 (or higher).
63 // PERF RECORD
64 // - The '-k mono' option tells 'perf record' to use CLOCK_MONOTONIC clock during sampling;
65 // which is required by 'perf inject', to make sure that both perf.data and jit-PID.dump
67 // PERF INJECT
68 // - The 'perf inject' tool injects information from jit-PID.dump into perf.data file,
71 // such location is recorded in perf.data file.
72 // The 'perf inject' tool is going to look for jit-PID.dump and generates small ELF files in
76 // 'perf inject' tool operates on this folder.
78 // - If you are executing 'perf inject' on non-Android devices (host), but perf.data and
81 // - Currently 'perf inject' doesn't provide option to change the path for jit-PID.dump and
83 // PERF ANNOTATE
84 // - The 'perf annotate' tool displays assembly level profiling report.
86 // - Make sure above small ELF files are available for 'perf annotate' tool to access,
110 // For perf-map profiling
116 // For perf-inject profiling