From 871480933a1c28f8a9fed4c4d34d06c439a7a422 Mon Sep 17 00:00:00 2001 From: Srikant Patnaik Date: Sun, 11 Jan 2015 12:28:04 +0530 Subject: Moved, renamed, and deleted files The original directory structure was scattered and unorganized. Changes are basically to make it look like kernel structure. --- ANDROID_3.4.5/tools/perf/CREDITS | 30 - ANDROID_3.4.5/tools/perf/Documentation/Makefile | 321 -- .../tools/perf/Documentation/asciidoc.conf | 91 - .../tools/perf/Documentation/examples.txt | 225 -- .../tools/perf/Documentation/manpage-1.72.xsl | 14 - .../tools/perf/Documentation/manpage-base.xsl | 35 - .../perf/Documentation/manpage-bold-literal.xsl | 17 - .../tools/perf/Documentation/manpage-normal.xsl | 13 - .../perf/Documentation/manpage-suppress-sp.xsl | 21 - .../tools/perf/Documentation/perf-annotate.txt | 90 - .../tools/perf/Documentation/perf-archive.txt | 22 - .../tools/perf/Documentation/perf-bench.txt | 120 - .../perf/Documentation/perf-buildid-cache.txt | 33 - .../tools/perf/Documentation/perf-buildid-list.txt | 43 - .../tools/perf/Documentation/perf-diff.txt | 74 - .../tools/perf/Documentation/perf-evlist.txt | 26 - .../tools/perf/Documentation/perf-help.txt | 38 - .../tools/perf/Documentation/perf-inject.txt | 35 - .../tools/perf/Documentation/perf-kmem.txt | 47 - .../tools/perf/Documentation/perf-kvm.txt | 74 - .../tools/perf/Documentation/perf-list.txt | 94 - .../tools/perf/Documentation/perf-lock.txt | 66 - .../tools/perf/Documentation/perf-probe.txt | 188 -- .../tools/perf/Documentation/perf-record.txt | 187 -- .../tools/perf/Documentation/perf-report.txt | 173 -- .../tools/perf/Documentation/perf-sched.txt | 55 - .../tools/perf/Documentation/perf-script-perl.txt | 216 -- .../perf/Documentation/perf-script-python.txt | 622 ---- .../tools/perf/Documentation/perf-script.txt | 209 -- .../tools/perf/Documentation/perf-stat.txt | 133 - .../tools/perf/Documentation/perf-test.txt | 28 - .../tools/perf/Documentation/perf-timechart.txt | 46 - .../tools/perf/Documentation/perf-top.txt | 193 -- ANDROID_3.4.5/tools/perf/Documentation/perf.txt | 24 - .../tools/perf/Documentation/perfconfig.example | 20 - ANDROID_3.4.5/tools/perf/MANIFEST | 15 - ANDROID_3.4.5/tools/perf/Makefile | 995 ------ ANDROID_3.4.5/tools/perf/arch/arm/Makefile | 4 - .../tools/perf/arch/arm/util/dwarf-regs.c | 67 - ANDROID_3.4.5/tools/perf/arch/powerpc/Makefile | 5 - .../tools/perf/arch/powerpc/util/dwarf-regs.c | 91 - .../tools/perf/arch/powerpc/util/header.c | 36 - ANDROID_3.4.5/tools/perf/arch/s390/Makefile | 4 - .../tools/perf/arch/s390/util/dwarf-regs.c | 22 - ANDROID_3.4.5/tools/perf/arch/sh/Makefile | 4 - ANDROID_3.4.5/tools/perf/arch/sh/util/dwarf-regs.c | 55 - ANDROID_3.4.5/tools/perf/arch/sparc/Makefile | 4 - .../tools/perf/arch/sparc/util/dwarf-regs.c | 43 - ANDROID_3.4.5/tools/perf/arch/x86/Makefile | 5 - .../tools/perf/arch/x86/util/dwarf-regs.c | 75 - ANDROID_3.4.5/tools/perf/arch/x86/util/header.c | 59 - ANDROID_3.4.5/tools/perf/bench/bench.h | 18 - ANDROID_3.4.5/tools/perf/bench/mem-memcpy-arch.h | 12 - .../tools/perf/bench/mem-memcpy-x86-64-asm-def.h | 12 - .../tools/perf/bench/mem-memcpy-x86-64-asm.S | 12 - ANDROID_3.4.5/tools/perf/bench/mem-memcpy.c | 303 -- ANDROID_3.4.5/tools/perf/bench/mem-memset-arch.h | 12 - .../tools/perf/bench/mem-memset-x86-64-asm-def.h | 12 - .../tools/perf/bench/mem-memset-x86-64-asm.S | 13 - ANDROID_3.4.5/tools/perf/bench/mem-memset.c | 297 -- ANDROID_3.4.5/tools/perf/bench/sched-messaging.c | 336 --- ANDROID_3.4.5/tools/perf/bench/sched-pipe.c | 127 - ANDROID_3.4.5/tools/perf/builtin-annotate.c | 317 -- ANDROID_3.4.5/tools/perf/builtin-bench.c | 248 -- ANDROID_3.4.5/tools/perf/builtin-buildid-cache.c | 132 - ANDROID_3.4.5/tools/perf/builtin-buildid-list.c | 109 - ANDROID_3.4.5/tools/perf/builtin-diff.c | 246 -- ANDROID_3.4.5/tools/perf/builtin-evlist.c | 54 - ANDROID_3.4.5/tools/perf/builtin-help.c | 459 --- ANDROID_3.4.5/tools/perf/builtin-inject.c | 276 -- ANDROID_3.4.5/tools/perf/builtin-kmem.c | 783 ----- ANDROID_3.4.5/tools/perf/builtin-kvm.c | 142 - ANDROID_3.4.5/tools/perf/builtin-list.c | 60 - ANDROID_3.4.5/tools/perf/builtin-lock.c | 1019 ------- ANDROID_3.4.5/tools/perf/builtin-probe.c | 404 --- ANDROID_3.4.5/tools/perf/builtin-record.c | 928 ------ ANDROID_3.4.5/tools/perf/builtin-report.c | 763 ----- ANDROID_3.4.5/tools/perf/builtin-sched.c | 1928 ------------ ANDROID_3.4.5/tools/perf/builtin-script.c | 1409 --------- ANDROID_3.4.5/tools/perf/builtin-stat.c | 1298 -------- ANDROID_3.4.5/tools/perf/builtin-test.c | 1782 ----------- ANDROID_3.4.5/tools/perf/builtin-timechart.c | 1124 ------- ANDROID_3.4.5/tools/perf/builtin-top.c | 1339 --------- ANDROID_3.4.5/tools/perf/builtin.h | 39 - ANDROID_3.4.5/tools/perf/command-list.txt | 25 - ANDROID_3.4.5/tools/perf/config/feature-tests.mak | 143 - ANDROID_3.4.5/tools/perf/config/utilities.mak | 188 -- ANDROID_3.4.5/tools/perf/design.txt | 462 --- ANDROID_3.4.5/tools/perf/perf-archive.sh | 47 - ANDROID_3.4.5/tools/perf/perf.c | 508 ---- ANDROID_3.4.5/tools/perf/perf.h | 237 -- ANDROID_3.4.5/tools/perf/python/twatch.py | 41 - .../perf/scripts/perl/Perf-Trace-Util/Context.c | 135 - .../perf/scripts/perl/Perf-Trace-Util/Context.xs | 42 - .../perf/scripts/perl/Perf-Trace-Util/Makefile.PL | 17 - .../tools/perf/scripts/perl/Perf-Trace-Util/README | 59 - .../perl/Perf-Trace-Util/lib/Perf/Trace/Context.pm | 55 - .../perl/Perf-Trace-Util/lib/Perf/Trace/Core.pm | 192 -- .../perl/Perf-Trace-Util/lib/Perf/Trace/Util.pm | 94 - .../perf/scripts/perl/Perf-Trace-Util/typemap | 1 - .../perf/scripts/perl/bin/check-perf-trace-record | 2 - .../perf/scripts/perl/bin/failed-syscalls-record | 2 - .../perf/scripts/perl/bin/failed-syscalls-report | 10 - .../tools/perf/scripts/perl/bin/rw-by-file-record | 3 - .../tools/perf/scripts/perl/bin/rw-by-file-report | 10 - .../tools/perf/scripts/perl/bin/rw-by-pid-record | 2 - .../tools/perf/scripts/perl/bin/rw-by-pid-report | 3 - .../tools/perf/scripts/perl/bin/rwtop-record | 2 - .../tools/perf/scripts/perl/bin/rwtop-report | 20 - .../perf/scripts/perl/bin/wakeup-latency-record | 6 - .../perf/scripts/perl/bin/wakeup-latency-report | 3 - .../perf/scripts/perl/bin/workqueue-stats-record | 2 - .../perf/scripts/perl/bin/workqueue-stats-report | 3 - .../tools/perf/scripts/perl/check-perf-trace.pl | 106 - .../tools/perf/scripts/perl/failed-syscalls.pl | 42 - .../tools/perf/scripts/perl/rw-by-file.pl | 106 - ANDROID_3.4.5/tools/perf/scripts/perl/rw-by-pid.pl | 184 -- ANDROID_3.4.5/tools/perf/scripts/perl/rwtop.pl | 199 -- .../tools/perf/scripts/perl/wakeup-latency.pl | 107 - .../tools/perf/scripts/perl/workqueue-stats.pl | 129 - .../perf/scripts/python/Perf-Trace-Util/Context.c | 88 - .../python/Perf-Trace-Util/lib/Perf/Trace/Core.py | 121 - .../Perf-Trace-Util/lib/Perf/Trace/SchedGui.py | 184 -- .../python/Perf-Trace-Util/lib/Perf/Trace/Util.py | 86 - .../python/bin/failed-syscalls-by-pid-record | 2 - .../python/bin/failed-syscalls-by-pid-report | 10 - .../scripts/python/bin/futex-contention-record | 2 - .../scripts/python/bin/futex-contention-report | 4 - .../perf/scripts/python/bin/net_dropmonitor-record | 2 - .../perf/scripts/python/bin/net_dropmonitor-report | 4 - .../perf/scripts/python/bin/netdev-times-record | 8 - .../perf/scripts/python/bin/netdev-times-report | 5 - .../perf/scripts/python/bin/sched-migration-record | 2 - .../perf/scripts/python/bin/sched-migration-report | 3 - .../tools/perf/scripts/python/bin/sctop-record | 2 - .../tools/perf/scripts/python/bin/sctop-report | 24 - .../python/bin/syscall-counts-by-pid-record | 2 - .../python/bin/syscall-counts-by-pid-report | 10 - .../perf/scripts/python/bin/syscall-counts-record | 2 - .../perf/scripts/python/bin/syscall-counts-report | 10 - .../tools/perf/scripts/python/check-perf-trace.py | 82 - .../perf/scripts/python/failed-syscalls-by-pid.py | 73 - .../tools/perf/scripts/python/futex-contention.py | 50 - .../tools/perf/scripts/python/net_dropmonitor.py | 72 - .../tools/perf/scripts/python/netdev-times.py | 464 --- .../tools/perf/scripts/python/sched-migration.py | 461 --- ANDROID_3.4.5/tools/perf/scripts/python/sctop.py | 75 - .../perf/scripts/python/syscall-counts-by-pid.py | 69 - .../tools/perf/scripts/python/syscall-counts.py | 59 - ANDROID_3.4.5/tools/perf/util/PERF-VERSION-GEN | 42 - ANDROID_3.4.5/tools/perf/util/abspath.c | 37 - ANDROID_3.4.5/tools/perf/util/alias.c | 77 - ANDROID_3.4.5/tools/perf/util/annotate.c | 611 ---- ANDROID_3.4.5/tools/perf/util/annotate.h | 107 - ANDROID_3.4.5/tools/perf/util/bitmap.c | 31 - ANDROID_3.4.5/tools/perf/util/build-id.c | 86 - ANDROID_3.4.5/tools/perf/util/build-id.h | 10 - ANDROID_3.4.5/tools/perf/util/cache.h | 102 - ANDROID_3.4.5/tools/perf/util/callchain.c | 461 --- ANDROID_3.4.5/tools/perf/util/callchain.h | 144 - ANDROID_3.4.5/tools/perf/util/cgroup.c | 177 -- ANDROID_3.4.5/tools/perf/util/cgroup.h | 17 - ANDROID_3.4.5/tools/perf/util/color.c | 325 -- ANDROID_3.4.5/tools/perf/util/color.h | 46 - ANDROID_3.4.5/tools/perf/util/config.c | 507 ---- ANDROID_3.4.5/tools/perf/util/cpumap.c | 195 -- ANDROID_3.4.5/tools/perf/util/cpumap.h | 17 - ANDROID_3.4.5/tools/perf/util/ctype.c | 39 - ANDROID_3.4.5/tools/perf/util/debug.c | 105 - ANDROID_3.4.5/tools/perf/util/debug.h | 36 - ANDROID_3.4.5/tools/perf/util/debugfs.c | 114 - ANDROID_3.4.5/tools/perf/util/debugfs.h | 12 - ANDROID_3.4.5/tools/perf/util/dwarf-aux.c | 843 ------ ANDROID_3.4.5/tools/perf/util/dwarf-aux.h | 111 - ANDROID_3.4.5/tools/perf/util/environment.c | 9 - ANDROID_3.4.5/tools/perf/util/event.c | 898 ------ ANDROID_3.4.5/tools/perf/util/event.h | 212 -- ANDROID_3.4.5/tools/perf/util/evlist.c | 866 ------ ANDROID_3.4.5/tools/perf/util/evlist.h | 125 - ANDROID_3.4.5/tools/perf/util/evsel.c | 677 ----- ANDROID_3.4.5/tools/perf/util/evsel.h | 175 -- ANDROID_3.4.5/tools/perf/util/exec_cmd.c | 148 - ANDROID_3.4.5/tools/perf/util/exec_cmd.h | 12 - ANDROID_3.4.5/tools/perf/util/generate-cmdlist.sh | 24 - ANDROID_3.4.5/tools/perf/util/gtk/browser.c | 189 -- ANDROID_3.4.5/tools/perf/util/gtk/gtk.h | 8 - ANDROID_3.4.5/tools/perf/util/header.c | 2452 --------------- ANDROID_3.4.5/tools/perf/util/header.h | 138 - ANDROID_3.4.5/tools/perf/util/help.c | 338 --- ANDROID_3.4.5/tools/perf/util/help.h | 29 - ANDROID_3.4.5/tools/perf/util/hist.c | 1362 --------- ANDROID_3.4.5/tools/perf/util/hist.h | 169 -- ANDROID_3.4.5/tools/perf/util/hweight.c | 31 - .../tools/perf/util/include/asm/alternative-asm.h | 8 - .../tools/perf/util/include/asm/asm-offsets.h | 1 - ANDROID_3.4.5/tools/perf/util/include/asm/bug.h | 22 - .../tools/perf/util/include/asm/byteorder.h | 2 - .../tools/perf/util/include/asm/cpufeature.h | 9 - ANDROID_3.4.5/tools/perf/util/include/asm/dwarf2.h | 13 - .../tools/perf/util/include/asm/hweight.h | 8 - ANDROID_3.4.5/tools/perf/util/include/asm/swab.h | 1 - ANDROID_3.4.5/tools/perf/util/include/asm/system.h | 1 - .../tools/perf/util/include/asm/uaccess.h | 14 - .../tools/perf/util/include/asm/unistd_32.h | 1 - .../tools/perf/util/include/asm/unistd_64.h | 1 - ANDROID_3.4.5/tools/perf/util/include/dwarf-regs.h | 8 - .../tools/perf/util/include/linux/bitmap.h | 46 - .../tools/perf/util/include/linux/bitops.h | 151 - .../tools/perf/util/include/linux/compiler.h | 14 - .../tools/perf/util/include/linux/const.h | 1 - .../tools/perf/util/include/linux/ctype.h | 1 - .../tools/perf/util/include/linux/export.h | 6 - ANDROID_3.4.5/tools/perf/util/include/linux/hash.h | 5 - .../tools/perf/util/include/linux/kernel.h | 111 - .../tools/perf/util/include/linux/linkage.h | 13 - ANDROID_3.4.5/tools/perf/util/include/linux/list.h | 29 - .../tools/perf/util/include/linux/poison.h | 1 - .../tools/perf/util/include/linux/prefetch.h | 6 - .../tools/perf/util/include/linux/rbtree.h | 1 - .../tools/perf/util/include/linux/string.h | 1 - .../tools/perf/util/include/linux/types.h | 21 - ANDROID_3.4.5/tools/perf/util/levenshtein.c | 84 - ANDROID_3.4.5/tools/perf/util/levenshtein.h | 8 - ANDROID_3.4.5/tools/perf/util/map.c | 715 ----- ANDROID_3.4.5/tools/perf/util/map.h | 258 -- ANDROID_3.4.5/tools/perf/util/pager.c | 96 - ANDROID_3.4.5/tools/perf/util/parse-events.c | 1062 ------- ANDROID_3.4.5/tools/perf/util/parse-events.h | 93 - ANDROID_3.4.5/tools/perf/util/parse-events.l | 127 - ANDROID_3.4.5/tools/perf/util/parse-events.y | 229 -- ANDROID_3.4.5/tools/perf/util/parse-options.c | 577 ---- ANDROID_3.4.5/tools/perf/util/parse-options.h | 192 -- ANDROID_3.4.5/tools/perf/util/path.c | 157 - ANDROID_3.4.5/tools/perf/util/pmu.c | 469 --- ANDROID_3.4.5/tools/perf/util/pmu.h | 41 - ANDROID_3.4.5/tools/perf/util/pmu.l | 43 - ANDROID_3.4.5/tools/perf/util/pmu.y | 93 - ANDROID_3.4.5/tools/perf/util/probe-event.c | 2097 ------------- ANDROID_3.4.5/tools/perf/util/probe-event.h | 138 - ANDROID_3.4.5/tools/perf/util/probe-finder.c | 1580 ---------- ANDROID_3.4.5/tools/perf/util/probe-finder.h | 107 - ANDROID_3.4.5/tools/perf/util/pstack.c | 75 - ANDROID_3.4.5/tools/perf/util/pstack.h | 14 - ANDROID_3.4.5/tools/perf/util/python-ext-sources | 19 - ANDROID_3.4.5/tools/perf/util/python.c | 1044 ------- ANDROID_3.4.5/tools/perf/util/quote.c | 54 - ANDROID_3.4.5/tools/perf/util/quote.h | 29 - ANDROID_3.4.5/tools/perf/util/run-command.c | 214 -- ANDROID_3.4.5/tools/perf/util/run-command.h | 58 - .../perf/util/scripting-engines/trace-event-perl.c | 634 ---- .../util/scripting-engines/trace-event-python.c | 600 ---- ANDROID_3.4.5/tools/perf/util/session.c | 1508 ---------- ANDROID_3.4.5/tools/perf/util/session.h | 160 - ANDROID_3.4.5/tools/perf/util/setup.py | 44 - ANDROID_3.4.5/tools/perf/util/sigchain.c | 52 - ANDROID_3.4.5/tools/perf/util/sigchain.h | 10 - ANDROID_3.4.5/tools/perf/util/sort.c | 528 ---- ANDROID_3.4.5/tools/perf/util/sort.h | 123 - ANDROID_3.4.5/tools/perf/util/strbuf.c | 134 - ANDROID_3.4.5/tools/perf/util/strbuf.h | 92 - ANDROID_3.4.5/tools/perf/util/strfilter.c | 199 -- ANDROID_3.4.5/tools/perf/util/strfilter.h | 48 - ANDROID_3.4.5/tools/perf/util/string.c | 315 -- ANDROID_3.4.5/tools/perf/util/strlist.c | 200 -- ANDROID_3.4.5/tools/perf/util/strlist.h | 78 - ANDROID_3.4.5/tools/perf/util/svghelper.c | 501 ---- ANDROID_3.4.5/tools/perf/util/svghelper.h | 28 - ANDROID_3.4.5/tools/perf/util/symbol.c | 2785 ----------------- ANDROID_3.4.5/tools/perf/util/symbol.h | 270 -- ANDROID_3.4.5/tools/perf/util/sysfs.c | 60 - ANDROID_3.4.5/tools/perf/util/sysfs.h | 6 - ANDROID_3.4.5/tools/perf/util/thread.c | 140 - ANDROID_3.4.5/tools/perf/util/thread.h | 44 - ANDROID_3.4.5/tools/perf/util/thread_map.c | 297 -- ANDROID_3.4.5/tools/perf/util/thread_map.h | 24 - ANDROID_3.4.5/tools/perf/util/tool.h | 50 - ANDROID_3.4.5/tools/perf/util/top.c | 104 - ANDROID_3.4.5/tools/perf/util/top.h | 55 - ANDROID_3.4.5/tools/perf/util/trace-event-info.c | 542 ---- ANDROID_3.4.5/tools/perf/util/trace-event-parse.c | 3153 -------------------- ANDROID_3.4.5/tools/perf/util/trace-event-read.c | 538 ---- .../tools/perf/util/trace-event-scripting.c | 166 -- ANDROID_3.4.5/tools/perf/util/trace-event.h | 317 -- ANDROID_3.4.5/tools/perf/util/types.h | 19 - ANDROID_3.4.5/tools/perf/util/ui/browser.c | 597 ---- ANDROID_3.4.5/tools/perf/util/ui/browser.h | 65 - .../tools/perf/util/ui/browsers/annotate.c | 433 --- ANDROID_3.4.5/tools/perf/util/ui/browsers/hists.c | 1341 --------- ANDROID_3.4.5/tools/perf/util/ui/browsers/map.c | 154 - ANDROID_3.4.5/tools/perf/util/ui/browsers/map.h | 6 - ANDROID_3.4.5/tools/perf/util/ui/helpline.c | 79 - ANDROID_3.4.5/tools/perf/util/ui/helpline.h | 16 - ANDROID_3.4.5/tools/perf/util/ui/keysyms.h | 27 - ANDROID_3.4.5/tools/perf/util/ui/libslang.h | 29 - ANDROID_3.4.5/tools/perf/util/ui/progress.c | 32 - ANDROID_3.4.5/tools/perf/util/ui/progress.h | 8 - ANDROID_3.4.5/tools/perf/util/ui/setup.c | 155 - ANDROID_3.4.5/tools/perf/util/ui/ui.h | 11 - ANDROID_3.4.5/tools/perf/util/ui/util.c | 250 -- ANDROID_3.4.5/tools/perf/util/ui/util.h | 14 - ANDROID_3.4.5/tools/perf/util/usage.c | 122 - ANDROID_3.4.5/tools/perf/util/util.c | 150 - ANDROID_3.4.5/tools/perf/util/util.h | 268 -- ANDROID_3.4.5/tools/perf/util/values.c | 232 -- ANDROID_3.4.5/tools/perf/util/values.h | 27 - ANDROID_3.4.5/tools/perf/util/wrapper.c | 40 - ANDROID_3.4.5/tools/perf/util/xyarray.c | 20 - ANDROID_3.4.5/tools/perf/util/xyarray.h | 20 - 308 files changed, 66486 deletions(-) delete mode 100644 ANDROID_3.4.5/tools/perf/CREDITS delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/Makefile delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/asciidoc.conf delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/examples.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/manpage-1.72.xsl delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/manpage-base.xsl delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/manpage-bold-literal.xsl delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/manpage-normal.xsl delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/manpage-suppress-sp.xsl delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-annotate.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-archive.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-bench.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-buildid-cache.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-buildid-list.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-diff.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-evlist.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-help.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-inject.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-kmem.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-kvm.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-list.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-lock.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-probe.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-record.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-report.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-sched.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-script-perl.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-script-python.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-script.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-stat.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-test.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-timechart.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf-top.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perf.txt delete mode 100644 ANDROID_3.4.5/tools/perf/Documentation/perfconfig.example delete mode 100644 ANDROID_3.4.5/tools/perf/MANIFEST delete mode 100644 ANDROID_3.4.5/tools/perf/Makefile delete mode 100644 ANDROID_3.4.5/tools/perf/arch/arm/Makefile delete mode 100644 ANDROID_3.4.5/tools/perf/arch/arm/util/dwarf-regs.c delete mode 100644 ANDROID_3.4.5/tools/perf/arch/powerpc/Makefile delete mode 100644 ANDROID_3.4.5/tools/perf/arch/powerpc/util/dwarf-regs.c delete mode 100644 ANDROID_3.4.5/tools/perf/arch/powerpc/util/header.c delete mode 100644 ANDROID_3.4.5/tools/perf/arch/s390/Makefile delete mode 100644 ANDROID_3.4.5/tools/perf/arch/s390/util/dwarf-regs.c delete mode 100644 ANDROID_3.4.5/tools/perf/arch/sh/Makefile delete mode 100644 ANDROID_3.4.5/tools/perf/arch/sh/util/dwarf-regs.c delete mode 100644 ANDROID_3.4.5/tools/perf/arch/sparc/Makefile delete mode 100644 ANDROID_3.4.5/tools/perf/arch/sparc/util/dwarf-regs.c delete mode 100644 ANDROID_3.4.5/tools/perf/arch/x86/Makefile delete mode 100644 ANDROID_3.4.5/tools/perf/arch/x86/util/dwarf-regs.c delete mode 100644 ANDROID_3.4.5/tools/perf/arch/x86/util/header.c delete mode 100644 ANDROID_3.4.5/tools/perf/bench/bench.h delete mode 100644 ANDROID_3.4.5/tools/perf/bench/mem-memcpy-arch.h delete mode 100644 ANDROID_3.4.5/tools/perf/bench/mem-memcpy-x86-64-asm-def.h delete mode 100644 ANDROID_3.4.5/tools/perf/bench/mem-memcpy-x86-64-asm.S delete mode 100644 ANDROID_3.4.5/tools/perf/bench/mem-memcpy.c delete mode 100644 ANDROID_3.4.5/tools/perf/bench/mem-memset-arch.h delete mode 100644 ANDROID_3.4.5/tools/perf/bench/mem-memset-x86-64-asm-def.h delete mode 100644 ANDROID_3.4.5/tools/perf/bench/mem-memset-x86-64-asm.S delete mode 100644 ANDROID_3.4.5/tools/perf/bench/mem-memset.c delete mode 100644 ANDROID_3.4.5/tools/perf/bench/sched-messaging.c delete mode 100644 ANDROID_3.4.5/tools/perf/bench/sched-pipe.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-annotate.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-bench.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-buildid-cache.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-buildid-list.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-diff.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-evlist.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-help.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-inject.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-kmem.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-kvm.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-list.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-lock.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-probe.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-record.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-report.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-sched.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-script.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-stat.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-test.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-timechart.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin-top.c delete mode 100644 ANDROID_3.4.5/tools/perf/builtin.h delete mode 100644 ANDROID_3.4.5/tools/perf/command-list.txt delete mode 100644 ANDROID_3.4.5/tools/perf/config/feature-tests.mak delete mode 100644 ANDROID_3.4.5/tools/perf/config/utilities.mak delete mode 100644 ANDROID_3.4.5/tools/perf/design.txt delete mode 100644 ANDROID_3.4.5/tools/perf/perf-archive.sh delete mode 100644 ANDROID_3.4.5/tools/perf/perf.c delete mode 100644 ANDROID_3.4.5/tools/perf/perf.h delete mode 100755 ANDROID_3.4.5/tools/perf/python/twatch.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/Perf-Trace-Util/Context.c delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/Perf-Trace-Util/Context.xs delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/Perf-Trace-Util/Makefile.PL delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/Perf-Trace-Util/README delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/Perf-Trace-Util/lib/Perf/Trace/Context.pm delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/Perf-Trace-Util/lib/Perf/Trace/Core.pm delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/Perf-Trace-Util/lib/Perf/Trace/Util.pm delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/Perf-Trace-Util/typemap delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/check-perf-trace-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/failed-syscalls-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/failed-syscalls-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/rw-by-file-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/rw-by-file-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/rw-by-pid-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/rw-by-pid-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/rwtop-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/rwtop-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/wakeup-latency-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/wakeup-latency-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/workqueue-stats-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/bin/workqueue-stats-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/check-perf-trace.pl delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/failed-syscalls.pl delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/rw-by-file.pl delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/rw-by-pid.pl delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/rwtop.pl delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/wakeup-latency.pl delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/perl/workqueue-stats.pl delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/Perf-Trace-Util/Context.c delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/Core.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/SchedGui.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/Util.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/failed-syscalls-by-pid-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/failed-syscalls-by-pid-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/futex-contention-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/futex-contention-report delete mode 100755 ANDROID_3.4.5/tools/perf/scripts/python/bin/net_dropmonitor-record delete mode 100755 ANDROID_3.4.5/tools/perf/scripts/python/bin/net_dropmonitor-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/netdev-times-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/netdev-times-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/sched-migration-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/sched-migration-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/sctop-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/sctop-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/syscall-counts-by-pid-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/syscall-counts-by-pid-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/syscall-counts-record delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/bin/syscall-counts-report delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/check-perf-trace.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/failed-syscalls-by-pid.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/futex-contention.py delete mode 100755 ANDROID_3.4.5/tools/perf/scripts/python/net_dropmonitor.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/netdev-times.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/sched-migration.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/sctop.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/syscall-counts-by-pid.py delete mode 100644 ANDROID_3.4.5/tools/perf/scripts/python/syscall-counts.py delete mode 100755 ANDROID_3.4.5/tools/perf/util/PERF-VERSION-GEN delete mode 100644 ANDROID_3.4.5/tools/perf/util/abspath.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/alias.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/annotate.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/annotate.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/bitmap.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/build-id.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/build-id.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/cache.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/callchain.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/callchain.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/cgroup.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/cgroup.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/color.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/color.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/config.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/cpumap.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/cpumap.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ctype.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/debug.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/debug.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/debugfs.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/debugfs.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/dwarf-aux.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/dwarf-aux.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/environment.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/event.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/event.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/evlist.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/evlist.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/evsel.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/evsel.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/exec_cmd.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/exec_cmd.h delete mode 100755 ANDROID_3.4.5/tools/perf/util/generate-cmdlist.sh delete mode 100644 ANDROID_3.4.5/tools/perf/util/gtk/browser.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/gtk/gtk.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/header.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/header.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/help.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/help.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/hist.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/hist.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/hweight.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/alternative-asm.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/asm-offsets.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/bug.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/byteorder.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/cpufeature.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/dwarf2.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/hweight.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/swab.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/system.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/uaccess.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/unistd_32.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/asm/unistd_64.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/dwarf-regs.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/bitmap.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/bitops.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/compiler.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/const.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/ctype.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/export.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/hash.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/kernel.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/linkage.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/list.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/poison.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/prefetch.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/rbtree.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/string.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/include/linux/types.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/levenshtein.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/levenshtein.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/map.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/map.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/pager.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/parse-events.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/parse-events.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/parse-events.l delete mode 100644 ANDROID_3.4.5/tools/perf/util/parse-events.y delete mode 100644 ANDROID_3.4.5/tools/perf/util/parse-options.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/parse-options.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/path.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/pmu.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/pmu.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/pmu.l delete mode 100644 ANDROID_3.4.5/tools/perf/util/pmu.y delete mode 100644 ANDROID_3.4.5/tools/perf/util/probe-event.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/probe-event.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/probe-finder.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/probe-finder.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/pstack.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/pstack.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/python-ext-sources delete mode 100644 ANDROID_3.4.5/tools/perf/util/python.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/quote.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/quote.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/run-command.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/run-command.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/scripting-engines/trace-event-perl.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/scripting-engines/trace-event-python.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/session.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/session.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/setup.py delete mode 100644 ANDROID_3.4.5/tools/perf/util/sigchain.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/sigchain.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/sort.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/sort.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/strbuf.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/strbuf.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/strfilter.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/strfilter.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/string.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/strlist.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/strlist.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/svghelper.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/svghelper.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/symbol.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/symbol.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/sysfs.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/sysfs.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/thread.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/thread.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/thread_map.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/thread_map.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/tool.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/top.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/top.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/trace-event-info.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/trace-event-parse.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/trace-event-read.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/trace-event-scripting.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/trace-event.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/types.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/browser.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/browser.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/browsers/annotate.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/browsers/hists.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/browsers/map.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/browsers/map.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/helpline.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/helpline.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/keysyms.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/libslang.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/progress.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/progress.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/setup.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/ui.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/util.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/ui/util.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/usage.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/util.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/util.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/values.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/values.h delete mode 100644 ANDROID_3.4.5/tools/perf/util/wrapper.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/xyarray.c delete mode 100644 ANDROID_3.4.5/tools/perf/util/xyarray.h (limited to 'ANDROID_3.4.5/tools/perf') diff --git a/ANDROID_3.4.5/tools/perf/CREDITS b/ANDROID_3.4.5/tools/perf/CREDITS deleted file mode 100644 index c2ddcb3a..00000000 --- a/ANDROID_3.4.5/tools/perf/CREDITS +++ /dev/null @@ -1,30 +0,0 @@ -Most of the infrastructure that 'perf' uses here has been reused -from the Git project, as of version: - - 66996ec: Sync with 1.6.2.4 - -Here is an (incomplete!) list of main contributors to those files -in util/* and elsewhere: - - Alex Riesen - Christian Couder - Dmitry Potapov - Jeff King - Johannes Schindelin - Johannes Sixt - Junio C Hamano - Linus Torvalds - Matthias Kestenholz - Michal Ostrowski - Miklos Vajna - Petr Baudis - Pierre Habouzit - René Scharfe - Samuel Tardieu - Shawn O. Pearce - Steffen Prohaska - Steve Haslam - -Thanks guys! - -The full history of the files can be found in the upstream Git commits. diff --git a/ANDROID_3.4.5/tools/perf/Documentation/Makefile b/ANDROID_3.4.5/tools/perf/Documentation/Makefile deleted file mode 100644 index ca600e09..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/Makefile +++ /dev/null @@ -1,321 +0,0 @@ -OUTPUT := ./ -ifeq ("$(origin O)", "command line") - ifneq ($(O),) - OUTPUT := $(O)/ - endif -endif - -MAN1_TXT= \ - $(filter-out $(addsuffix .txt, $(ARTICLES) $(SP_ARTICLES)), \ - $(wildcard perf-*.txt)) \ - perf.txt -MAN5_TXT= -MAN7_TXT= - -MAN_TXT = $(MAN1_TXT) $(MAN5_TXT) $(MAN7_TXT) -_MAN_XML=$(patsubst %.txt,%.xml,$(MAN_TXT)) -_MAN_HTML=$(patsubst %.txt,%.html,$(MAN_TXT)) - -MAN_XML=$(addprefix $(OUTPUT),$(_MAN_XML)) -MAN_HTML=$(addprefix $(OUTPUT),$(_MAN_HTML)) - -ARTICLES = -# with their own formatting rules. -SP_ARTICLES = -API_DOCS = $(patsubst %.txt,%,$(filter-out technical/api-index-skel.txt technical/api-index.txt, $(wildcard technical/api-*.txt))) -SP_ARTICLES += $(API_DOCS) -SP_ARTICLES += technical/api-index - -_DOC_HTML = $(_MAN_HTML) -_DOC_HTML+=$(patsubst %,%.html,$(ARTICLES) $(SP_ARTICLES)) -DOC_HTML=$(addprefix $(OUTPUT),$(_DOC_HTML)) - -_DOC_MAN1=$(patsubst %.txt,%.1,$(MAN1_TXT)) -_DOC_MAN5=$(patsubst %.txt,%.5,$(MAN5_TXT)) -_DOC_MAN7=$(patsubst %.txt,%.7,$(MAN7_TXT)) - -DOC_MAN1=$(addprefix $(OUTPUT),$(_DOC_MAN1)) -DOC_MAN5=$(addprefix $(OUTPUT),$(_DOC_MAN5)) -DOC_MAN7=$(addprefix $(OUTPUT),$(_DOC_MAN7)) - -# Make the path relative to DESTDIR, not prefix -ifndef DESTDIR -prefix?=$(HOME) -endif -bindir?=$(prefix)/bin -htmldir?=$(prefix)/share/doc/perf-doc -pdfdir?=$(prefix)/share/doc/perf-doc -mandir?=$(prefix)/share/man -man1dir=$(mandir)/man1 -man5dir=$(mandir)/man5 -man7dir=$(mandir)/man7 - -ASCIIDOC=asciidoc -ASCIIDOC_EXTRA = --unsafe -MANPAGE_XSL = manpage-normal.xsl -XMLTO_EXTRA = -INSTALL?=install -RM ?= rm -f -DOC_REF = origin/man -HTML_REF = origin/html - -infodir?=$(prefix)/share/info -MAKEINFO=makeinfo -INSTALL_INFO=install-info -DOCBOOK2X_TEXI=docbook2x-texi -DBLATEX=dblatex -ifndef PERL_PATH - PERL_PATH = /usr/bin/perl -endif - --include ../config.mak.autogen --include ../config.mak - -# -# For asciidoc ... -# -7.1.2, no extra settings are needed. -# 8.0-, set ASCIIDOC8. -# - -# -# For docbook-xsl ... -# -1.68.1, set ASCIIDOC_NO_ROFF? (based on changelog from 1.73.0) -# 1.69.0, no extra settings are needed? -# 1.69.1-1.71.0, set DOCBOOK_SUPPRESS_SP? -# 1.71.1, no extra settings are needed? -# 1.72.0, set DOCBOOK_XSL_172. -# 1.73.0-, set ASCIIDOC_NO_ROFF -# - -# -# If you had been using DOCBOOK_XSL_172 in an attempt to get rid -# of 'the ".ft C" problem' in your generated manpages, and you -# instead ended up with weird characters around callouts, try -# using ASCIIDOC_NO_ROFF instead (it works fine with ASCIIDOC8). -# - -ifdef ASCIIDOC8 -ASCIIDOC_EXTRA += -a asciidoc7compatible -endif -ifdef DOCBOOK_XSL_172 -ASCIIDOC_EXTRA += -a perf-asciidoc-no-roff -MANPAGE_XSL = manpage-1.72.xsl -else - ifdef ASCIIDOC_NO_ROFF - # docbook-xsl after 1.72 needs the regular XSL, but will not - # pass-thru raw roff codes from asciidoc.conf, so turn them off. - ASCIIDOC_EXTRA += -a perf-asciidoc-no-roff - endif -endif -ifdef MAN_BOLD_LITERAL -XMLTO_EXTRA += -m manpage-bold-literal.xsl -endif -ifdef DOCBOOK_SUPPRESS_SP -XMLTO_EXTRA += -m manpage-suppress-sp.xsl -endif - -SHELL_PATH ?= $(SHELL) -# Shell quote; -SHELL_PATH_SQ = $(subst ','\'',$(SHELL_PATH)) - -# -# Please note that there is a minor bug in asciidoc. -# The version after 6.0.3 _will_ include the patch found here: -# http://marc.theaimsgroup.com/?l=perf&m=111558757202243&w=2 -# -# Until that version is released you may have to apply the patch -# yourself - yes, all 6 characters of it! -# - -QUIET_SUBDIR0 = +$(MAKE) -C # space to separate -C and subdir -QUIET_SUBDIR1 = - -ifneq ($(findstring $(MAKEFLAGS),w),w) -PRINT_DIR = --no-print-directory -else # "make -w" -NO_SUBDIR = : -endif - -ifneq ($(findstring $(MAKEFLAGS),s),s) -ifndef V - QUIET_ASCIIDOC = @echo ' ' ASCIIDOC $@; - QUIET_XMLTO = @echo ' ' XMLTO $@; - QUIET_DB2TEXI = @echo ' ' DB2TEXI $@; - QUIET_MAKEINFO = @echo ' ' MAKEINFO $@; - QUIET_DBLATEX = @echo ' ' DBLATEX $@; - QUIET_XSLTPROC = @echo ' ' XSLTPROC $@; - QUIET_GEN = @echo ' ' GEN $@; - QUIET_STDERR = 2> /dev/null - QUIET_SUBDIR0 = +@subdir= - QUIET_SUBDIR1 = ;$(NO_SUBDIR) echo ' ' SUBDIR $$subdir; \ - $(MAKE) $(PRINT_DIR) -C $$subdir - export V -endif -endif - -all: html man - -html: $(DOC_HTML) - -$(DOC_HTML) $(DOC_MAN1) $(DOC_MAN5) $(DOC_MAN7): asciidoc.conf - -man: man1 man5 man7 -man1: $(DOC_MAN1) -man5: $(DOC_MAN5) -man7: $(DOC_MAN7) - -info: $(OUTPUT)perf.info $(OUTPUT)perfman.info - -pdf: $(OUTPUT)user-manual.pdf - -install: install-man - -install-man: man - $(INSTALL) -d -m 755 $(DESTDIR)$(man1dir) -# $(INSTALL) -d -m 755 $(DESTDIR)$(man5dir) -# $(INSTALL) -d -m 755 $(DESTDIR)$(man7dir) - $(INSTALL) -m 644 $(DOC_MAN1) $(DESTDIR)$(man1dir) -# $(INSTALL) -m 644 $(DOC_MAN5) $(DESTDIR)$(man5dir) -# $(INSTALL) -m 644 $(DOC_MAN7) $(DESTDIR)$(man7dir) - -install-info: info - $(INSTALL) -d -m 755 $(DESTDIR)$(infodir) - $(INSTALL) -m 644 $(OUTPUT)perf.info $(OUTPUT)perfman.info $(DESTDIR)$(infodir) - if test -r $(DESTDIR)$(infodir)/dir; then \ - $(INSTALL_INFO) --info-dir=$(DESTDIR)$(infodir) perf.info ;\ - $(INSTALL_INFO) --info-dir=$(DESTDIR)$(infodir) perfman.info ;\ - else \ - echo "No directory found in $(DESTDIR)$(infodir)" >&2 ; \ - fi - -install-pdf: pdf - $(INSTALL) -d -m 755 $(DESTDIR)$(pdfdir) - $(INSTALL) -m 644 $(OUTPUT)user-manual.pdf $(DESTDIR)$(pdfdir) - -#install-html: html -# '$(SHELL_PATH_SQ)' ./install-webdoc.sh $(DESTDIR)$(htmldir) - -../PERF-VERSION-FILE: .FORCE-PERF-VERSION-FILE - $(QUIET_SUBDIR0)../ $(QUIET_SUBDIR1) PERF-VERSION-FILE - --include ../PERF-VERSION-FILE - -# -# Determine "include::" file references in asciidoc files. -# -$(OUTPUT)doc.dep : $(wildcard *.txt) build-docdep.perl - $(QUIET_GEN)$(RM) $@+ $@ && \ - $(PERL_PATH) ./build-docdep.perl >$@+ $(QUIET_STDERR) && \ - mv $@+ $@ - --include $(OUPTUT)doc.dep - -_cmds_txt = cmds-ancillaryinterrogators.txt \ - cmds-ancillarymanipulators.txt \ - cmds-mainporcelain.txt \ - cmds-plumbinginterrogators.txt \ - cmds-plumbingmanipulators.txt \ - cmds-synchingrepositories.txt \ - cmds-synchelpers.txt \ - cmds-purehelpers.txt \ - cmds-foreignscminterface.txt -cmds_txt=$(addprefix $(OUTPUT),$(_cmds_txt)) - -$(cmds_txt): $(OUTPUT)cmd-list.made - -$(OUTPUT)cmd-list.made: cmd-list.perl ../command-list.txt $(MAN1_TXT) - $(QUIET_GEN)$(RM) $@ && \ - $(PERL_PATH) ./cmd-list.perl ../command-list.txt $(QUIET_STDERR) && \ - date >$@ - -clean: - $(RM) $(MAN_XML) $(addsuffix +,$(MAN_XML)) - $(RM) $(MAN_HTML) $(addsuffix +,$(MAN_HTML)) - $(RM) $(DOC_HTML) $(DOC_MAN1) $(DOC_MAN5) $(DOC_MAN7) - $(RM) $(OUTPUT)*.texi $(OUTPUT)*.texi+ $(OUTPUT)*.texi++ - $(RM) $(OUTPUT)perf.info $(OUTPUT)perfman.info - $(RM) $(OUTPUT)howto-index.txt $(OUTPUT)howto/*.html $(OUTPUT)doc.dep - $(RM) $(OUTPUT)technical/api-*.html $(OUTPUT)technical/api-index.txt - $(RM) $(cmds_txt) $(OUTPUT)*.made - -$(MAN_HTML): $(OUTPUT)%.html : %.txt - $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \ - $(ASCIIDOC) -b xhtml11 -d manpage -f asciidoc.conf \ - $(ASCIIDOC_EXTRA) -aperf_version=$(PERF_VERSION) -o $@+ $< && \ - mv $@+ $@ - -$(OUTPUT)%.1 $(OUTPUT)%.5 $(OUTPUT)%.7 : $(OUTPUT)%.xml - $(QUIET_XMLTO)$(RM) $@ && \ - xmlto -o $(OUTPUT) -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $< - -$(OUTPUT)%.xml : %.txt - $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \ - $(ASCIIDOC) -b docbook -d manpage -f asciidoc.conf \ - $(ASCIIDOC_EXTRA) -aperf_version=$(PERF_VERSION) -o $@+ $< && \ - mv $@+ $@ - -XSLT = docbook.xsl -XSLTOPTS = --xinclude --stringparam html.stylesheet docbook-xsl.css - -$(OUTPUT)user-manual.html: $(OUTPUT)user-manual.xml - $(QUIET_XSLTPROC)xsltproc $(XSLTOPTS) -o $@ $(XSLT) $< - -$(OUTPUT)perf.info: $(OUTPUT)user-manual.texi - $(QUIET_MAKEINFO)$(MAKEINFO) --no-split -o $@ $(OUTPUT)user-manual.texi - -$(OUTPUT)user-manual.texi: $(OUTPUT)user-manual.xml - $(QUIET_DB2TEXI)$(RM) $@+ $@ && \ - $(DOCBOOK2X_TEXI) $(OUTPUT)user-manual.xml --encoding=UTF-8 --to-stdout >$@++ && \ - $(PERL_PATH) fix-texi.perl <$@++ >$@+ && \ - rm $@++ && \ - mv $@+ $@ - -$(OUTPUT)user-manual.pdf: $(OUTPUT)user-manual.xml - $(QUIET_DBLATEX)$(RM) $@+ $@ && \ - $(DBLATEX) -o $@+ -p /etc/asciidoc/dblatex/asciidoc-dblatex.xsl -s /etc/asciidoc/dblatex/asciidoc-dblatex.sty $< && \ - mv $@+ $@ - -$(OUTPUT)perfman.texi: $(MAN_XML) cat-texi.perl - $(QUIET_DB2TEXI)$(RM) $@+ $@ && \ - ($(foreach xml,$(MAN_XML),$(DOCBOOK2X_TEXI) --encoding=UTF-8 \ - --to-stdout $(xml) &&) true) > $@++ && \ - $(PERL_PATH) cat-texi.perl $@ <$@++ >$@+ && \ - rm $@++ && \ - mv $@+ $@ - -$(OUTPUT)perfman.info: $(OUTPUT)perfman.texi - $(QUIET_MAKEINFO)$(MAKEINFO) --no-split --no-validate $*.texi - -$(patsubst %.txt,%.texi,$(MAN_TXT)): %.texi : %.xml - $(QUIET_DB2TEXI)$(RM) $@+ $@ && \ - $(DOCBOOK2X_TEXI) --to-stdout $*.xml >$@+ && \ - mv $@+ $@ - -howto-index.txt: howto-index.sh $(wildcard howto/*.txt) - $(QUIET_GEN)$(RM) $@+ $@ && \ - '$(SHELL_PATH_SQ)' ./howto-index.sh $(wildcard howto/*.txt) >$@+ && \ - mv $@+ $@ - -$(patsubst %,%.html,$(ARTICLES)) : %.html : %.txt - $(QUIET_ASCIIDOC)$(ASCIIDOC) -b xhtml11 $*.txt - -WEBDOC_DEST = /pub/software/tools/perf/docs - -$(patsubst %.txt,%.html,$(wildcard howto/*.txt)): %.html : %.txt - $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \ - sed -e '1,/^$$/d' $< | $(ASCIIDOC) -b xhtml11 - >$@+ && \ - mv $@+ $@ - -# UNIMPLEMENTED -#install-webdoc : html -# '$(SHELL_PATH_SQ)' ./install-webdoc.sh $(WEBDOC_DEST) - -# quick-install: quick-install-man - -# quick-install-man: -# '$(SHELL_PATH_SQ)' ./install-doc-quick.sh $(DOC_REF) $(DESTDIR)$(mandir) - -#quick-install-html: -# '$(SHELL_PATH_SQ)' ./install-doc-quick.sh $(HTML_REF) $(DESTDIR)$(htmldir) - -.PHONY: .FORCE-PERF-VERSION-FILE diff --git a/ANDROID_3.4.5/tools/perf/Documentation/asciidoc.conf b/ANDROID_3.4.5/tools/perf/Documentation/asciidoc.conf deleted file mode 100644 index 356b23a4..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/asciidoc.conf +++ /dev/null @@ -1,91 +0,0 @@ -## linkperf: macro -# -# Usage: linkperf:command[manpage-section] -# -# Note, {0} is the manpage section, while {target} is the command. -# -# Show PERF link as: (
); if section is defined, else just show -# the command. - -[macros] -(?su)[\\]?(?Plinkperf):(?P\S*?)\[(?P.*?)\]= - -[attributes] -asterisk=* -plus=+ -caret=^ -startsb=[ -endsb=] -tilde=~ - -ifdef::backend-docbook[] -[linkperf-inlinemacro] -{0%{target}} -{0#} -{0#{target}{0}} -{0#} -endif::backend-docbook[] - -ifdef::backend-docbook[] -ifndef::perf-asciidoc-no-roff[] -# "unbreak" docbook-xsl v1.68 for manpages. v1.69 works with or without this. -# v1.72 breaks with this because it replaces dots not in roff requests. -[listingblock] -{title} - -ifdef::doctype-manpage[] - .ft C -endif::doctype-manpage[] -| -ifdef::doctype-manpage[] - .ft -endif::doctype-manpage[] - -{title#} -endif::perf-asciidoc-no-roff[] - -ifdef::perf-asciidoc-no-roff[] -ifdef::doctype-manpage[] -# The following two small workarounds insert a simple paragraph after screen -[listingblock] -{title} - -| - -{title#} - -[verseblock] -{title} -{title%} -{title#} -| - -{title#} -{title%} -endif::doctype-manpage[] -endif::perf-asciidoc-no-roff[] -endif::backend-docbook[] - -ifdef::doctype-manpage[] -ifdef::backend-docbook[] -[header] -template::[header-declarations] - - -{mantitle} -{manvolnum} -perf -{perf_version} -perf Manual - - - {manname} - {manpurpose} - -endif::backend-docbook[] -endif::doctype-manpage[] - -ifdef::backend-xhtml11[] -[linkperf-inlinemacro] -{target}{0?({0})} -endif::backend-xhtml11[] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/examples.txt b/ANDROID_3.4.5/tools/perf/Documentation/examples.txt deleted file mode 100644 index 77f95276..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/examples.txt +++ /dev/null @@ -1,225 +0,0 @@ - - ------------------------------ - ****** perf by examples ****** - ------------------------------ - -[ From an e-mail by Ingo Molnar, http://lkml.org/lkml/2009/8/4/346 ] - - -First, discovery/enumeration of available counters can be done via -'perf list': - -titan:~> perf list - [...] - kmem:kmalloc [Tracepoint event] - kmem:kmem_cache_alloc [Tracepoint event] - kmem:kmalloc_node [Tracepoint event] - kmem:kmem_cache_alloc_node [Tracepoint event] - kmem:kfree [Tracepoint event] - kmem:kmem_cache_free [Tracepoint event] - kmem:mm_page_free [Tracepoint event] - kmem:mm_page_free_batched [Tracepoint event] - kmem:mm_page_alloc [Tracepoint event] - kmem:mm_page_alloc_zone_locked [Tracepoint event] - kmem:mm_page_pcpu_drain [Tracepoint event] - kmem:mm_page_alloc_extfrag [Tracepoint event] - -Then any (or all) of the above event sources can be activated and -measured. For example the page alloc/free properties of a 'hackbench -run' are: - - titan:~> perf stat -e kmem:mm_page_pcpu_drain -e kmem:mm_page_alloc - -e kmem:mm_page_free_batched -e kmem:mm_page_free ./hackbench 10 - Time: 0.575 - - Performance counter stats for './hackbench 10': - - 13857 kmem:mm_page_pcpu_drain - 27576 kmem:mm_page_alloc - 6025 kmem:mm_page_free_batched - 20934 kmem:mm_page_free - - 0.613972165 seconds time elapsed - -You can observe the statistical properties as well, by using the -'repeat the workload N times' feature of perf stat: - - titan:~> perf stat --repeat 5 -e kmem:mm_page_pcpu_drain -e - kmem:mm_page_alloc -e kmem:mm_page_free_batched -e - kmem:mm_page_free ./hackbench 10 - Time: 0.627 - Time: 0.644 - Time: 0.564 - Time: 0.559 - Time: 0.626 - - Performance counter stats for './hackbench 10' (5 runs): - - 12920 kmem:mm_page_pcpu_drain ( +- 3.359% ) - 25035 kmem:mm_page_alloc ( +- 3.783% ) - 6104 kmem:mm_page_free_batched ( +- 0.934% ) - 18376 kmem:mm_page_free ( +- 4.941% ) - - 0.643954516 seconds time elapsed ( +- 2.363% ) - -Furthermore, these tracepoints can be used to sample the workload as -well. For example the page allocations done by a 'git gc' can be -captured the following way: - - titan:~/git> perf record -f -e kmem:mm_page_alloc -c 1 ./git gc - Counting objects: 1148, done. - Delta compression using up to 2 threads. - Compressing objects: 100% (450/450), done. - Writing objects: 100% (1148/1148), done. - Total 1148 (delta 690), reused 1148 (delta 690) - [ perf record: Captured and wrote 0.267 MB perf.data (~11679 samples) ] - -To check which functions generated page allocations: - - titan:~/git> perf report - # Samples: 10646 - # - # Overhead Command Shared Object - # ........ ............... .......................... - # - 23.57% git-repack /lib64/libc-2.5.so - 21.81% git /lib64/libc-2.5.so - 14.59% git ./git - 11.79% git-repack ./git - 7.12% git /lib64/ld-2.5.so - 3.16% git-repack /lib64/libpthread-2.5.so - 2.09% git-repack /bin/bash - 1.97% rm /lib64/libc-2.5.so - 1.39% mv /lib64/ld-2.5.so - 1.37% mv /lib64/libc-2.5.so - 1.12% git-repack /lib64/ld-2.5.so - 0.95% rm /lib64/ld-2.5.so - 0.90% git-update-serv /lib64/libc-2.5.so - 0.73% git-update-serv /lib64/ld-2.5.so - 0.68% perf /lib64/libpthread-2.5.so - 0.64% git-repack /usr/lib64/libz.so.1.2.3 - -Or to see it on a more finegrained level: - -titan:~/git> perf report --sort comm,dso,symbol -# Samples: 10646 -# -# Overhead Command Shared Object Symbol -# ........ ............... .......................... ...... -# - 9.35% git-repack ./git [.] insert_obj_hash - 9.12% git ./git [.] insert_obj_hash - 7.31% git /lib64/libc-2.5.so [.] memcpy - 6.34% git-repack /lib64/libc-2.5.so [.] _int_malloc - 6.24% git-repack /lib64/libc-2.5.so [.] memcpy - 5.82% git-repack /lib64/libc-2.5.so [.] __GI___fork - 5.47% git /lib64/libc-2.5.so [.] _int_malloc - 2.99% git /lib64/libc-2.5.so [.] memset - -Furthermore, call-graph sampling can be done too, of page -allocations - to see precisely what kind of page allocations there -are: - - titan:~/git> perf record -f -g -e kmem:mm_page_alloc -c 1 ./git gc - Counting objects: 1148, done. - Delta compression using up to 2 threads. - Compressing objects: 100% (450/450), done. - Writing objects: 100% (1148/1148), done. - Total 1148 (delta 690), reused 1148 (delta 690) - [ perf record: Captured and wrote 0.963 MB perf.data (~42069 samples) ] - - titan:~/git> perf report -g - # Samples: 10686 - # - # Overhead Command Shared Object - # ........ ............... .......................... - # - 23.25% git-repack /lib64/libc-2.5.so - | - |--50.00%-- _int_free - | - |--37.50%-- __GI___fork - | make_child - | - |--12.50%-- ptmalloc_unlock_all2 - | make_child - | - --6.25%-- __GI_strcpy - 21.61% git /lib64/libc-2.5.so - | - |--30.00%-- __GI_read - | | - | --83.33%-- git_config_from_file - | git_config - | | - [...] - -Or you can observe the whole system's page allocations for 10 -seconds: - -titan:~/git> perf stat -a -e kmem:mm_page_pcpu_drain -e -kmem:mm_page_alloc -e kmem:mm_page_free_batched -e -kmem:mm_page_free sleep 10 - - Performance counter stats for 'sleep 10': - - 171585 kmem:mm_page_pcpu_drain - 322114 kmem:mm_page_alloc - 73623 kmem:mm_page_free_batched - 254115 kmem:mm_page_free - - 10.000591410 seconds time elapsed - -Or observe how fluctuating the page allocations are, via statistical -analysis done over ten 1-second intervals: - - titan:~/git> perf stat --repeat 10 -a -e kmem:mm_page_pcpu_drain -e - kmem:mm_page_alloc -e kmem:mm_page_free_batched -e - kmem:mm_page_free sleep 1 - - Performance counter stats for 'sleep 1' (10 runs): - - 17254 kmem:mm_page_pcpu_drain ( +- 3.709% ) - 34394 kmem:mm_page_alloc ( +- 4.617% ) - 7509 kmem:mm_page_free_batched ( +- 4.820% ) - 25653 kmem:mm_page_free ( +- 3.672% ) - - 1.058135029 seconds time elapsed ( +- 3.089% ) - -Or you can annotate the recorded 'git gc' run on a per symbol basis -and check which instructions/source-code generated page allocations: - - titan:~/git> perf annotate __GI___fork - ------------------------------------------------ - Percent | Source code & Disassembly of libc-2.5.so - ------------------------------------------------ - : - : - : Disassembly of section .plt: - : Disassembly of section .text: - : - : 00000031a2e95560 <__fork>: - [...] - 0.00 : 31a2e95602: b8 38 00 00 00 mov $0x38,%eax - 0.00 : 31a2e95607: 0f 05 syscall - 83.42 : 31a2e95609: 48 3d 00 f0 ff ff cmp $0xfffffffffffff000,%rax - 0.00 : 31a2e9560f: 0f 87 4d 01 00 00 ja 31a2e95762 <__fork+0x202> - 0.00 : 31a2e95615: 85 c0 test %eax,%eax - -( this shows that 83.42% of __GI___fork's page allocations come from - the 0x38 system call it performs. ) - -etc. etc. - a lot more is possible. I could list a dozen of -other different usecases straight away - neither of which is -possible via /proc/vmstat. - -/proc/vmstat is not in the same league really, in terms of -expressive power of system analysis and performance -analysis. - -All that the above results needed were those new tracepoints -in include/tracing/events/kmem.h. - - Ingo - - diff --git a/ANDROID_3.4.5/tools/perf/Documentation/manpage-1.72.xsl b/ANDROID_3.4.5/tools/perf/Documentation/manpage-1.72.xsl deleted file mode 100644 index b4d315cb..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/manpage-1.72.xsl +++ /dev/null @@ -1,14 +0,0 @@ - - - - - - -▓ -⌂ - - diff --git a/ANDROID_3.4.5/tools/perf/Documentation/manpage-base.xsl b/ANDROID_3.4.5/tools/perf/Documentation/manpage-base.xsl deleted file mode 100644 index a264fa61..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/manpage-base.xsl +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - - - - - - - - - sp - - - - - - - - br - - - diff --git a/ANDROID_3.4.5/tools/perf/Documentation/manpage-bold-literal.xsl b/ANDROID_3.4.5/tools/perf/Documentation/manpage-bold-literal.xsl deleted file mode 100644 index 608eb5df..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/manpage-bold-literal.xsl +++ /dev/null @@ -1,17 +0,0 @@ - - - - - - - fB - - - fR - - - diff --git a/ANDROID_3.4.5/tools/perf/Documentation/manpage-normal.xsl b/ANDROID_3.4.5/tools/perf/Documentation/manpage-normal.xsl deleted file mode 100644 index a48f5b11..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/manpage-normal.xsl +++ /dev/null @@ -1,13 +0,0 @@ - - - - - - -\ -. - - diff --git a/ANDROID_3.4.5/tools/perf/Documentation/manpage-suppress-sp.xsl b/ANDROID_3.4.5/tools/perf/Documentation/manpage-suppress-sp.xsl deleted file mode 100644 index a63c7632..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/manpage-suppress-sp.xsl +++ /dev/null @@ -1,21 +0,0 @@ - - - - - - - - - - - - - - - diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-annotate.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-annotate.txt deleted file mode 100644 index c89f9e14..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-annotate.txt +++ /dev/null @@ -1,90 +0,0 @@ -perf-annotate(1) -================ - -NAME ----- -perf-annotate - Read perf.data (created by perf record) and display annotated code - -SYNOPSIS --------- -[verse] -'perf annotate' [-i | --input=file] [symbol_name] - -DESCRIPTION ------------ -This command reads the input file and displays an annotated version of the -code. If the object file has debug symbols then the source code will be -displayed alongside assembly code. - -If there is no debug info in the object, then annotated assembly is displayed. - -OPTIONS -------- --i:: ---input=:: - Input file name. (default: perf.data unless stdin is a fifo) - --d:: ---dsos=:: - Only consider symbols in these dsos. --s:: ---symbol=:: - Symbol to annotate. - --f:: ---force:: - Don't complain, do it. - --v:: ---verbose:: - Be more verbose. (Show symbol address, etc) - --D:: ---dump-raw-trace:: - Dump raw trace in ASCII. - --k:: ---vmlinux=:: - vmlinux pathname. - --m:: ---modules:: - Load module symbols. WARNING: use only with -k and LIVE kernel. - --l:: ---print-line:: - Print matching source lines (may be slow). - --P:: ---full-paths:: - Don't shorten the displayed pathnames. - ---stdio:: Use the stdio interface. - ---tui:: Use the TUI interface Use of --tui requires a tty, if one is not - present, as when piping to other commands, the stdio interface is - used. This interfaces starts by centering on the line with more - samples, TAB/UNTAB cycles through the lines with more samples. - --C:: ---cpu:: Only report samples for the list of CPUs provided. Multiple CPUs can - be provided as a comma-separated list with no space: 0,1. Ranges of - CPUs are specified with -: 0-2. Default is to report samples on all - CPUs. - ---asm-raw:: - Show raw instruction encoding of assembly instructions. - ---source:: - Interleave source code with assembly code. Enabled by default, - disable with --no-source. - ---symfs=:: - Look for files with symbols relative to this directory. - --M:: ---disassembler-style=:: Set disassembler style for objdump. - -SEE ALSO --------- -linkperf:perf-record[1], linkperf:perf-report[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-archive.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-archive.txt deleted file mode 100644 index fae174dc..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-archive.txt +++ /dev/null @@ -1,22 +0,0 @@ -perf-archive(1) -=============== - -NAME ----- -perf-archive - Create archive with object files with build-ids found in perf.data file - -SYNOPSIS --------- -[verse] -'perf archive' [file] - -DESCRIPTION ------------ -This command runs runs perf-buildid-list --with-hits, and collects the files -with the buildids found so that analisys of perf.data contents can be possible -on another machine. - - -SEE ALSO --------- -linkperf:perf-record[1], linkperf:perf-buildid-list[1], linkperf:perf-report[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-bench.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-bench.txt deleted file mode 100644 index a3dbadb2..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-bench.txt +++ /dev/null @@ -1,120 +0,0 @@ -perf-bench(1) -============= - -NAME ----- -perf-bench - General framework for benchmark suites - -SYNOPSIS --------- -[verse] -'perf bench' [] [] - -DESCRIPTION ------------ -This 'perf bench' command is general framework for benchmark suites. - -COMMON OPTIONS --------------- --f:: ---format=:: -Specify format style. -Current available format styles are: - -'default':: -Default style. This is mainly for human reading. ---------------------- -% perf bench sched pipe # with no style specified -(executing 1000000 pipe operations between two tasks) - Total time:5.855 sec - 5.855061 usecs/op - 170792 ops/sec ---------------------- - -'simple':: -This simple style is friendly for automated -processing by scripts. ---------------------- -% perf bench --format=simple sched pipe # specified simple -5.988 ---------------------- - -SUBSYSTEM ---------- - -'sched':: - Scheduler and IPC mechanisms. - -SUITES FOR 'sched' -~~~~~~~~~~~~~~~~~~ -*messaging*:: -Suite for evaluating performance of scheduler and IPC mechanisms. -Based on hackbench by Rusty Russell. - -Options of *pipe* -^^^^^^^^^^^^^^^^^ --p:: ---pipe:: -Use pipe() instead of socketpair() - --t:: ---thread:: -Be multi thread instead of multi process - --g:: ---group=:: -Specify number of groups - --l:: ---loop=:: -Specify number of loops - -Example of *messaging* -^^^^^^^^^^^^^^^^^^^^^^ - ---------------------- -% perf bench sched messaging # run with default -options (20 sender and receiver processes per group) -(10 groups == 400 processes run) - - Total time:0.308 sec - -% perf bench sched messaging -t -g 20 # be multi-thread, with 20 groups -(20 sender and receiver threads per group) -(20 groups == 800 threads run) - - Total time:0.582 sec ---------------------- - -*pipe*:: -Suite for pipe() system call. -Based on pipe-test-1m.c by Ingo Molnar. - -Options of *pipe* -^^^^^^^^^^^^^^^^^ --l:: ---loop=:: -Specify number of loops. - -Example of *pipe* -^^^^^^^^^^^^^^^^^ - ---------------------- -% perf bench sched pipe -(executing 1000000 pipe operations between two tasks) - - Total time:8.091 sec - 8.091833 usecs/op - 123581 ops/sec - -% perf bench sched pipe -l 1000 # loop 1000 -(executing 1000 pipe operations between two tasks) - - Total time:0.016 sec - 16.948000 usecs/op - 59004 ops/sec ---------------------- - -SEE ALSO --------- -linkperf:perf[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-buildid-cache.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-buildid-cache.txt deleted file mode 100644 index c1057701..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-buildid-cache.txt +++ /dev/null @@ -1,33 +0,0 @@ -perf-buildid-cache(1) -===================== - -NAME ----- -perf-buildid-cache - Manage build-id cache. - -SYNOPSIS --------- -[verse] -'perf buildid-cache ' - -DESCRIPTION ------------ -This command manages the build-id cache. It can add and remove files to/from -the cache. In the future it should as well purge older entries, set upper -limits for the space used by the cache, etc. - -OPTIONS -------- --a:: ---add=:: - Add specified file to the cache. --r:: ---remove=:: - Remove specified file from the cache. --v:: ---verbose:: - Be more verbose. - -SEE ALSO --------- -linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-buildid-list[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-buildid-list.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-buildid-list.txt deleted file mode 100644 index 25c52efc..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-buildid-list.txt +++ /dev/null @@ -1,43 +0,0 @@ -perf-buildid-list(1) -==================== - -NAME ----- -perf-buildid-list - List the buildids in a perf.data file - -SYNOPSIS --------- -[verse] -'perf buildid-list ' - -DESCRIPTION ------------ -This command displays the buildids found in a perf.data file, so that other -tools can be used to fetch packages with matching symbol tables for use by -perf report. - -It can also be used to show the build id of the running kernel or in an ELF -file using -i/--input. - -OPTIONS -------- --H:: ---with-hits:: - Show only DSOs with hits. --i:: ---input=:: - Input file name. (default: perf.data unless stdin is a fifo) --f:: ---force:: - Don't do ownership validation. --k:: ---kernel:: - Show running kernel build id. --v:: ---verbose:: - Be more verbose. - -SEE ALSO --------- -linkperf:perf-record[1], linkperf:perf-top[1], -linkperf:perf-report[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-diff.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-diff.txt deleted file mode 100644 index 74d7481e..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-diff.txt +++ /dev/null @@ -1,74 +0,0 @@ -perf-diff(1) -============ - -NAME ----- -perf-diff - Read two perf.data files and display the differential profile - -SYNOPSIS --------- -[verse] -'perf diff' [oldfile] [newfile] - -DESCRIPTION ------------ -This command displays the performance difference amongst two perf.data files -captured via perf record. - -If no parameters are passed it will assume perf.data.old and perf.data. - -OPTIONS -------- --M:: ---displacement:: - Show position displacement relative to baseline. - --D:: ---dump-raw-trace:: - Dump raw trace in ASCII. - --m:: ---modules:: - Load module symbols. WARNING: use only with -k and LIVE kernel - --d:: ---dsos=:: - Only consider symbols in these dsos. CSV that understands - file://filename entries. - --C:: ---comms=:: - Only consider symbols in these comms. CSV that understands - file://filename entries. - --S:: ---symbols=:: - Only consider these symbols. CSV that understands - file://filename entries. - --s:: ---sort=:: - Sort by key(s): pid, comm, dso, symbol. - --t:: ---field-separator=:: - - Use a special separator character and don't pad with spaces, replacing - all occurrences of this separator in symbol names (and other output) - with a '.' character, that thus it's the only non valid separator. - --v:: ---verbose:: - Be verbose, for instance, show the raw counts in addition to the - diff. - --f:: ---force:: - Don't complain, do it. - ---symfs=:: - Look for files with symbols relative to this directory. - -SEE ALSO --------- -linkperf:perf-record[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-evlist.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-evlist.txt deleted file mode 100644 index 0507ec7b..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-evlist.txt +++ /dev/null @@ -1,26 +0,0 @@ -perf-evlist(1) -============== - -NAME ----- -perf-evlist - List the event names in a perf.data file - -SYNOPSIS --------- -[verse] -'perf evlist ' - -DESCRIPTION ------------ -This command displays the names of events sampled in a perf.data file. - -OPTIONS -------- --i:: ---input=:: - Input file name. (default: perf.data unless stdin is a fifo) - -SEE ALSO --------- -linkperf:perf-record[1], linkperf:perf-list[1], -linkperf:perf-report[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-help.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-help.txt deleted file mode 100644 index 51439181..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-help.txt +++ /dev/null @@ -1,38 +0,0 @@ -perf-help(1) -============ - -NAME ----- -perf-help - display help information about perf - -SYNOPSIS --------- -'perf help' [-a|--all] [COMMAND] - -DESCRIPTION ------------ - -With no options and no COMMAND given, the synopsis of the 'perf' -command and a list of the most commonly used perf commands are printed -on the standard output. - -If the option '--all' or '-a' is given, then all available commands are -printed on the standard output. - -If a perf command is named, a manual page for that command is brought -up. The 'man' program is used by default for this purpose, but this -can be overridden by other options or configuration variables. - -Note that `perf --help ...` is identical to `perf help ...` because the -former is internally converted into the latter. - -OPTIONS -------- --a:: ---all:: - Prints all the available commands on the standard output. This - option supersedes any other option. - -PERF ----- -Part of the linkperf:perf[1] suite diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-inject.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-inject.txt deleted file mode 100644 index 025630d4..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-inject.txt +++ /dev/null @@ -1,35 +0,0 @@ -perf-inject(1) -============== - -NAME ----- -perf-inject - Filter to augment the events stream with additional information - -SYNOPSIS --------- -[verse] -'perf inject ' - -DESCRIPTION ------------ -perf-inject reads a perf-record event stream and repipes it to stdout. At any -point the processing code can inject other events into the event stream - in -this case build-ids (-b option) are read and injected as needed into the event -stream. - -Build-ids are just the first user of perf-inject - potentially anything that -needs userspace processing to augment the events stream with additional -information could make use of this facility. - -OPTIONS -------- --b:: ---build-ids=:: - Inject build-ids into the output stream --v:: ---verbose:: - Be more verbose. - -SEE ALSO --------- -linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-kmem.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-kmem.txt deleted file mode 100644 index 7c8fbbf3..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-kmem.txt +++ /dev/null @@ -1,47 +0,0 @@ -perf-kmem(1) -============ - -NAME ----- -perf-kmem - Tool to trace/measure kernel memory(slab) properties - -SYNOPSIS --------- -[verse] -'perf kmem' {record|stat} [] - -DESCRIPTION ------------ -There are two variants of perf kmem: - - 'perf kmem record ' to record the kmem events - of an arbitrary workload. - - 'perf kmem stat' to report kernel memory statistics. - -OPTIONS -------- --i :: ---input=:: - Select the input file (default: perf.data unless stdin is a fifo) - ---caller:: - Show per-callsite statistics - ---alloc:: - Show per-allocation statistics - --s :: ---sort=:: - Sort the output (default: frag,hit,bytes) - --l :: ---line=:: - Print n lines only - ---raw-ip:: - Print raw ip instead of symbol - -SEE ALSO --------- -linkperf:perf-record[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-kvm.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-kvm.txt deleted file mode 100644 index dd84cb2f..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-kvm.txt +++ /dev/null @@ -1,74 +0,0 @@ -perf-kvm(1) -=========== - -NAME ----- -perf-kvm - Tool to trace/measure kvm guest os - -SYNOPSIS --------- -[verse] -'perf kvm' [--host] [--guest] [--guestmount= - [--guestkallsyms= --guestmodules= | --guestvmlinux=]] - {top|record|report|diff|buildid-list} -'perf kvm' [--host] [--guest] [--guestkallsyms= --guestmodules= - | --guestvmlinux=] {top|record|report|diff|buildid-list} - -DESCRIPTION ------------ -There are a couple of variants of perf kvm: - - 'perf kvm [options] top ' to generates and displays - a performance counter profile of guest os in realtime - of an arbitrary workload. - - 'perf kvm record ' to record the performance counter profile - of an arbitrary workload and save it into a perf data file. If both - --host and --guest are input, the perf data file name is perf.data.kvm. - If there is no --host but --guest, the file name is perf.data.guest. - If there is no --guest but --host, the file name is perf.data.host. - - 'perf kvm report' to display the performance counter profile information - recorded via perf kvm record. - - 'perf kvm diff' to displays the performance difference amongst two perf.data - files captured via perf record. - - 'perf kvm buildid-list' to display the buildids found in a perf data file, - so that other tools can be used to fetch packages with matching symbol tables - for use by perf report. - -OPTIONS -------- --i:: ---input=:: - Input file name. --o:: ---output:: - Output file name. ---host=:: - Collect host side performance profile. ---guest=:: - Collect guest side performance profile. ---guestmount=:: - Guest os root file system mount directory. Users mounts guest os - root directories under by a specific filesystem access method, - typically, sshfs. For example, start 2 guest os. The one's pid is 8888 - and the other's is 9999. - #mkdir ~/guestmount; cd ~/guestmount - #sshfs -o allow_other,direct_io -p 5551 localhost:/ 8888/ - #sshfs -o allow_other,direct_io -p 5552 localhost:/ 9999/ - #perf kvm --host --guest --guestmount=~/guestmount top ---guestkallsyms=:: - Guest os /proc/kallsyms file copy. 'perf' kvm' reads it to get guest - kernel symbols. Users copy it out from guest os. ---guestmodules=:: - Guest os /proc/modules file copy. 'perf' kvm' reads it to get guest - kernel module information. Users copy it out from guest os. ---guestvmlinux=:: - Guest os kernel vmlinux. - -SEE ALSO --------- -linkperf:perf-top[1], linkperf:perf-record[1], linkperf:perf-report[1], -linkperf:perf-diff[1], linkperf:perf-buildid-list[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-list.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-list.txt deleted file mode 100644 index ddc22525..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-list.txt +++ /dev/null @@ -1,94 +0,0 @@ -perf-list(1) -============ - -NAME ----- -perf-list - List all symbolic event types - -SYNOPSIS --------- -[verse] -'perf list' [hw|sw|cache|tracepoint|event_glob] - -DESCRIPTION ------------ -This command displays the symbolic event types which can be selected in the -various perf commands with the -e option. - -EVENT MODIFIERS ---------------- - -Events can optionally have a modifer by appending a colon and one or -more modifiers. Modifiers allow the user to restrict when events are -counted with 'u' for user-space, 'k' for kernel, 'h' for hypervisor. -Additional modifiers are 'G' for guest counting (in KVM guests) and 'H' -for host counting (not in KVM guests). - -The 'p' modifier can be used for specifying how precise the instruction -address should be. The 'p' modifier is currently only implemented for -Intel PEBS and can be specified multiple times: - 0 - SAMPLE_IP can have arbitrary skid - 1 - SAMPLE_IP must have constant skid - 2 - SAMPLE_IP requested to have 0 skid - 3 - SAMPLE_IP must have 0 skid - -The PEBS implementation now supports up to 2. - -RAW HARDWARE EVENT DESCRIPTOR ------------------------------ -Even when an event is not available in a symbolic form within perf right now, -it can be encoded in a per processor specific way. - -For instance For x86 CPUs NNN represents the raw register encoding with the -layout of IA32_PERFEVTSELx MSRs (see [Intel® 64 and IA-32 Architectures Software Developer's Manual Volume 3B: System Programming Guide] Figure 30-1 Layout -of IA32_PERFEVTSELx MSRs) or AMD's PerfEvtSeln (see [AMD64 Architecture Programmer’s Manual Volume 2: System Programming], Page 344, -Figure 13-7 Performance Event-Select Register (PerfEvtSeln)). - -Example: - -If the Intel docs for a QM720 Core i7 describe an event as: - - Event Umask Event Mask - Num. Value Mnemonic Description Comment - - A8H 01H LSD.UOPS Counts the number of micro-ops Use cmask=1 and - delivered by loop stream detector invert to count - cycles - -raw encoding of 0x1A8 can be used: - - perf stat -e r1a8 -a sleep 1 - perf record -e r1a8 ... - -You should refer to the processor specific documentation for getting these -details. Some of them are referenced in the SEE ALSO section below. - -OPTIONS -------- - -Without options all known events will be listed. - -To limit the list use: - -. 'hw' or 'hardware' to list hardware events such as cache-misses, etc. - -. 'sw' or 'software' to list software events such as context switches, etc. - -. 'cache' or 'hwcache' to list hardware cache events such as L1-dcache-loads, etc. - -. 'tracepoint' to list all tracepoint events, alternatively use - 'subsys_glob:event_glob' to filter by tracepoint subsystems such as sched, - block, etc. - -. If none of the above is matched, it will apply the supplied glob to all - events, printing the ones that match. - -One or more types can be used at the same time, listing the events for the -types specified. - -SEE ALSO --------- -linkperf:perf-stat[1], linkperf:perf-top[1], -linkperf:perf-record[1], -http://www.intel.com/Assets/PDF/manual/253669.pdf[Intel® 64 and IA-32 Architectures Software Developer's Manual Volume 3B: System Programming Guide], -http://support.amd.com/us/Processor_TechDocs/24593.pdf[AMD64 Architecture Programmer’s Manual Volume 2: System Programming] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-lock.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-lock.txt deleted file mode 100644 index c7f5f556..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-lock.txt +++ /dev/null @@ -1,66 +0,0 @@ -perf-lock(1) -============ - -NAME ----- -perf-lock - Analyze lock events - -SYNOPSIS --------- -[verse] -'perf lock' {record|report|script|info} - -DESCRIPTION ------------ -You can analyze various lock behaviours -and statistics with this 'perf lock' command. - - 'perf lock record ' records lock events - between start and end . And this command - produces the file "perf.data" which contains tracing - results of lock events. - - 'perf lock report' reports statistical data. - - 'perf lock script' shows raw lock events. - - 'perf lock info' shows metadata like threads or addresses - of lock instances. - -COMMON OPTIONS --------------- - --i:: ---input=:: - Input file name. (default: perf.data unless stdin is a fifo) - --v:: ---verbose:: - Be more verbose (show symbol address, etc). - --D:: ---dump-raw-trace:: - Dump raw trace in ASCII. - -REPORT OPTIONS --------------- - --k:: ---key=:: - Sorting key. Possible values: acquired (default), contended, - wait_total, wait_max, wait_min. - -INFO OPTIONS ------------- - --t:: ---threads:: - dump thread list in perf.data - --m:: ---map:: - dump map of lock instances (address:name table) - -SEE ALSO --------- -linkperf:perf[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-probe.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-probe.txt deleted file mode 100644 index 2780d9ce..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-probe.txt +++ /dev/null @@ -1,188 +0,0 @@ -perf-probe(1) -============= - -NAME ----- -perf-probe - Define new dynamic tracepoints - -SYNOPSIS --------- -[verse] -'perf probe' [options] --add='PROBE' [...] -or -'perf probe' [options] PROBE -or -'perf probe' [options] --del='[GROUP:]EVENT' [...] -or -'perf probe' --list -or -'perf probe' [options] --line='LINE' -or -'perf probe' [options] --vars='PROBEPOINT' - -DESCRIPTION ------------ -This command defines dynamic tracepoint events, by symbol and registers -without debuginfo, or by C expressions (C line numbers, C function names, -and C local variables) with debuginfo. - - -OPTIONS -------- --k:: ---vmlinux=PATH:: - Specify vmlinux path which has debuginfo (Dwarf binary). - --m:: ---module=MODNAME|PATH:: - Specify module name in which perf-probe searches probe points - or lines. If a path of module file is passed, perf-probe - treat it as an offline module (this means you can add a probe on - a module which has not been loaded yet). - --s:: ---source=PATH:: - Specify path to kernel source. - --v:: ---verbose:: - Be more verbose (show parsed arguments, etc). - --a:: ---add=:: - Define a probe event (see PROBE SYNTAX for detail). - --d:: ---del=:: - Delete probe events. This accepts glob wildcards('*', '?') and character - classes(e.g. [a-z], [!A-Z]). - --l:: ---list:: - List up current probe events. - --L:: ---line=:: - Show source code lines which can be probed. This needs an argument - which specifies a range of the source code. (see LINE SYNTAX for detail) - --V:: ---vars=:: - Show available local variables at given probe point. The argument - syntax is same as PROBE SYNTAX, but NO ARGs. - ---externs:: - (Only for --vars) Show external defined variables in addition to local - variables. - --F:: ---funcs:: - Show available functions in given module or kernel. - ---filter=FILTER:: - (Only for --vars and --funcs) Set filter. FILTER is a combination of glob - pattern, see FILTER PATTERN for detail. - Default FILTER is "!__k???tab_* & !__crc_*" for --vars, and "!_*" - for --funcs. - If several filters are specified, only the last filter is used. - --f:: ---force:: - Forcibly add events with existing name. - --n:: ---dry-run:: - Dry run. With this option, --add and --del doesn't execute actual - adding and removal operations. - ---max-probes:: - Set the maximum number of probe points for an event. Default is 128. - -PROBE SYNTAX ------------- -Probe points are defined by following syntax. - - 1) Define event based on function name - [EVENT=]FUNC[@SRC][:RLN|+OFFS|%return|;PTN] [ARG ...] - - 2) Define event based on source file with line number - [EVENT=]SRC:ALN [ARG ...] - - 3) Define event based on source file with lazy pattern - [EVENT=]SRC;PTN [ARG ...] - - -'EVENT' specifies the name of new event, if omitted, it will be set the name of the probed function. Currently, event group name is set as 'probe'. -'FUNC' specifies a probed function name, and it may have one of the following options; '+OFFS' is the offset from function entry address in bytes, ':RLN' is the relative-line number from function entry line, and '%return' means that it probes function return. And ';PTN' means lazy matching pattern (see LAZY MATCHING). Note that ';PTN' must be the end of the probe point definition. In addition, '@SRC' specifies a source file which has that function. -It is also possible to specify a probe point by the source line number or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is the source file path, ':ALN' is the line number and ';PTN' is the lazy matching pattern. -'ARG' specifies the arguments of this probe point, (see PROBE ARGUMENT). - -PROBE ARGUMENT --------------- -Each probe argument follows below syntax. - - [NAME=]LOCALVAR|$retval|%REG|@SYMBOL[:TYPE] - -'NAME' specifies the name of this argument (optional). You can use the name of local variable, local data structure member (e.g. var->field, var.field2), local array with fixed index (e.g. array[1], var->array[0], var->pointer[2]), or kprobe-tracer argument format (e.g. $retval, %ax, etc). Note that the name of this argument will be set as the last member name if you specify a local data structure member (e.g. field2 for 'var->field1.field2'.) -'TYPE' casts the type of this argument (optional). If omitted, perf probe automatically set the type based on debuginfo. You can specify 'string' type only for the local variable or structure member which is an array of or a pointer to 'char' or 'unsigned char' type. - -LINE SYNTAX ------------ -Line range is described by following syntax. - - "FUNC[@SRC][:RLN[+NUM|-RLN2]]|SRC[:ALN[+NUM|-ALN2]]" - -FUNC specifies the function name of showing lines. 'RLN' is the start line -number from function entry line, and 'RLN2' is the end line number. As same as -probe syntax, 'SRC' means the source file path, 'ALN' is start line number, -and 'ALN2' is end line number in the file. It is also possible to specify how -many lines to show by using 'NUM'. Moreover, 'FUNC@SRC' combination is good -for searching a specific function when several functions share same name. -So, "source.c:100-120" shows lines between 100th to l20th in source.c file. And "func:10+20" shows 20 lines from 10th line of func function. - -LAZY MATCHING -------------- - The lazy line matching is similar to glob matching but ignoring spaces in both of pattern and target. So this accepts wildcards('*', '?') and character classes(e.g. [a-z], [!A-Z]). - -e.g. - 'a=*' can matches 'a=b', 'a = b', 'a == b' and so on. - -This provides some sort of flexibility and robustness to probe point definitions against minor code changes. For example, actual 10th line of schedule() can be moved easily by modifying schedule(), but the same line matching 'rq=cpu_rq*' may still exist in the function.) - -FILTER PATTERN --------------- - The filter pattern is a glob matching pattern(s) to filter variables. - In addition, you can use "!" for specifying filter-out rule. You also can give several rules combined with "&" or "|", and fold those rules as one rule by using "(" ")". - -e.g. - With --filter "foo* | bar*", perf probe -V shows variables which start with "foo" or "bar". - With --filter "!foo* & *bar", perf probe -V shows variables which don't start with "foo" and end with "bar", like "fizzbar". But "foobar" is filtered out. - -EXAMPLES --------- -Display which lines in schedule() can be probed: - - ./perf probe --line schedule - -Add a probe on schedule() function 12th line with recording cpu local variable: - - ./perf probe schedule:12 cpu - or - ./perf probe --add='schedule:12 cpu' - - this will add one or more probes which has the name start with "schedule". - - Add probes on lines in schedule() function which calls update_rq_clock(). - - ./perf probe 'schedule;update_rq_clock*' - or - ./perf probe --add='schedule;update_rq_clock*' - -Delete all probes on schedule(). - - ./perf probe --del='schedule*' - - -SEE ALSO --------- -linkperf:perf-trace[1], linkperf:perf-record[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-record.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-record.txt deleted file mode 100644 index a1386b2f..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-record.txt +++ /dev/null @@ -1,187 +0,0 @@ -perf-record(1) -============== - -NAME ----- -perf-record - Run a command and record its profile into perf.data - -SYNOPSIS --------- -[verse] -'perf record' [-e | --event=EVENT] [-l] [-a] -'perf record' [-e | --event=EVENT] [-l] [-a] -- [] - -DESCRIPTION ------------ -This command runs a command and gathers a performance counter profile -from it, into perf.data - without displaying anything. - -This file can then be inspected later on, using 'perf report'. - - -OPTIONS -------- -...:: - Any command you can specify in a shell. - --e:: ---event=:: - Select the PMU event. Selection can be: - - - a symbolic event name (use 'perf list' to list all events) - - - a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a - hexadecimal event descriptor. - - - a hardware breakpoint event in the form of '\mem:addr[:access]' - where addr is the address in memory you want to break in. - Access is the memory access type (read, write, execute) it can - be passed as follows: '\mem:addr[:[r][w][x]]'. - If you want to profile read-write accesses in 0x1000, just set - 'mem:0x1000:rw'. - ---filter=:: - Event filter. - --a:: ---all-cpus:: - System-wide collection from all CPUs. - --l:: - Scale counter values. - --p:: ---pid=:: - Record events on existing process ID (comma separated list). - --t:: ---tid=:: - Record events on existing thread ID (comma separated list). - --u:: ---uid=:: - Record events in threads owned by uid. Name or number. - --r:: ---realtime=:: - Collect data with this RT SCHED_FIFO priority. --D:: ---no-delay:: - Collect data without buffering. --A:: ---append:: - Append to the output file to do incremental profiling. - --f:: ---force:: - Overwrite existing data file. (deprecated) - --c:: ---count=:: - Event period to sample. - --o:: ---output=:: - Output file name. - --i:: ---no-inherit:: - Child tasks do not inherit counters. --F:: ---freq=:: - Profile at this frequency. - --m:: ---mmap-pages=:: - Number of mmap data pages. Must be a power of two. - --g:: ---call-graph:: - Do call-graph (stack chain/backtrace) recording. - --q:: ---quiet:: - Don't print any message, useful for scripting. - --v:: ---verbose:: - Be more verbose (show counter open errors, etc). - --s:: ---stat:: - Per thread counts. - --d:: ---data:: - Sample addresses. - --T:: ---timestamp:: - Sample timestamps. Use it with 'perf report -D' to see the timestamps, - for instance. - --n:: ---no-samples:: - Don't sample. - --R:: ---raw-samples:: -Collect raw sample records from all opened counters (default for tracepoint counters). - --C:: ---cpu:: -Collect samples only on the list of CPUs provided. Multiple CPUs can be provided as a -comma-separated list with no space: 0,1. Ranges of CPUs are specified with -: 0-2. -In per-thread mode with inheritance mode on (default), samples are captured only when -the thread executes on the designated CPUs. Default is to monitor all CPUs. - --N:: ---no-buildid-cache:: -Do not update the builid cache. This saves some overhead in situations -where the information in the perf.data file (which includes buildids) -is sufficient. - --G name,...:: ---cgroup name,...:: -monitor only in the container (cgroup) called "name". This option is available only -in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to -container "name" are monitored when they run on the monitored CPUs. Multiple cgroups -can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup -to first event, second cgroup to second event and so on. It is possible to provide -an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have -corresponding events, i.e., they always refer to events defined earlier on the command -line. - --b:: ---branch-any:: -Enable taken branch stack sampling. Any type of taken branch may be sampled. -This is a shortcut for --branch-filter any. See --branch-filter for more infos. - --j:: ---branch-filter:: -Enable taken branch stack sampling. Each sample captures a series of consecutive -taken branches. The number of branches captured with each sample depends on the -underlying hardware, the type of branches of interest, and the executed code. -It is possible to select the types of branches captured by enabling filters. The -following filters are defined: - - - any: any type of branches - - any_call: any function call or system call - - any_ret: any function return or system call return - - any_ind: any indirect branch - - u: only when the branch target is at the user level - - k: only when the branch target is in the kernel - - hv: only when the target is at the hypervisor level - -+ -The option requires at least one branch type among any, any_call, any_ret, ind_call. -The privilege levels may be ommitted, in which case, the privilege levels of the associated -event are applied to the branch filter. Both kernel (k) and hypervisor (hv) privilege -levels are subject to permissions. When sampling on multiple events, branch stack sampling -is enabled for all the sampling events. The sampled branch type is the same for all events. -The various filters must be specified as a comma separated list: --branch-filter any_ret,u,k -Note that this feature may not be available on all processors. - -SEE ALSO --------- -linkperf:perf-stat[1], linkperf:perf-list[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-report.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-report.txt deleted file mode 100644 index 2d89f027..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-report.txt +++ /dev/null @@ -1,173 +0,0 @@ -perf-report(1) -============== - -NAME ----- -perf-report - Read perf.data (created by perf record) and display the profile - -SYNOPSIS --------- -[verse] -'perf report' [-i | --input=file] - -DESCRIPTION ------------ -This command displays the performance counter profile information recorded -via perf record. - -OPTIONS -------- --i:: ---input=:: - Input file name. (default: perf.data unless stdin is a fifo) - --v:: ---verbose:: - Be more verbose. (show symbol address, etc) - --d:: ---dsos=:: - Only consider symbols in these dsos. CSV that understands - file://filename entries. --n:: ---show-nr-samples:: - Show the number of samples for each symbol - ---showcpuutilization:: - Show sample percentage for different cpu modes. - --T:: ---threads:: - Show per-thread event counters --c:: ---comms=:: - Only consider symbols in these comms. CSV that understands - file://filename entries. --S:: ---symbols=:: - Only consider these symbols. CSV that understands - file://filename entries. - ---symbol-filter=:: - Only show symbols that match (partially) with this filter. - --U:: ---hide-unresolved:: - Only display entries resolved to a symbol. - --s:: ---sort=:: - Sort by key(s): pid, comm, dso, symbol, parent. - --p:: ---parent=:: - regex filter to identify parent, see: '--sort parent' - --x:: ---exclude-other:: - Only display entries with parent-match. - --w:: ---column-widths=:: - Force each column width to the provided list, for large terminal - readability. - --t:: ---field-separator=:: - - Use a special separator character and don't pad with spaces, replacing - all occurrences of this separator in symbol names (and other output) - with a '.' character, that thus it's the only non valid separator. - --D:: ---dump-raw-trace:: - Dump raw trace in ASCII. - --g [type,min[,limit],order]:: ---call-graph:: - Display call chains using type, min percent threshold, optional print - limit and order. - type can be either: - - flat: single column, linear exposure of call chains. - - graph: use a graph tree, displaying absolute overhead rates. - - fractal: like graph, but displays relative rates. Each branch of - the tree is considered as a new profiled object. + - - order can be either: - - callee: callee based call graph. - - caller: inverted caller based call graph. - - Default: fractal,0.5,callee. - --G:: ---inverted:: - alias for inverted caller based call graph. - ---pretty=:: - Pretty printing style. key: normal, raw - ---stdio:: Use the stdio interface. - ---tui:: Use the TUI interface, that is integrated with annotate and allows - zooming into DSOs or threads, among other features. Use of --tui - requires a tty, if one is not present, as when piping to other - commands, the stdio interface is used. - ---gtk:: Use the GTK2 interface. - --k:: ---vmlinux=:: - vmlinux pathname - ---kallsyms=:: - kallsyms pathname - --m:: ---modules:: - Load module symbols. WARNING: This should only be used with -k and - a LIVE kernel. - --f:: ---force:: - Don't complain, do it. - ---symfs=:: - Look for files with symbols relative to this directory. - --C:: ---cpu:: Only report samples for the list of CPUs provided. Multiple CPUs can - be provided as a comma-separated list with no space: 0,1. Ranges of - CPUs are specified with -: 0-2. Default is to report samples on all - CPUs. - --M:: ---disassembler-style=:: Set disassembler style for objdump. - ---source:: - Interleave source code with assembly code. Enabled by default, - disable with --no-source. - ---asm-raw:: - Show raw instruction encoding of assembly instructions. - ---show-total-period:: Show a column with the sum of periods. - --I:: ---show-info:: - Display extended information about the perf.data file. This adds - information which may be very large and thus may clutter the display. - It currently includes: cpu and numa topology of the host system. - --b:: ---branch-stack:: - Use the addresses of sampled taken branches instead of the instruction - address to build the histograms. To generate meaningful output, the - perf.data file must have been obtained using perf record -b or - perf record --branch-filter xxx where xxx is a branch filter option. - perf report is able to auto-detect whether a perf.data file contains - branch stacks and it will automatically switch to the branch view mode, - unless --no-branch-stack is used. - -SEE ALSO --------- -linkperf:perf-stat[1], linkperf:perf-annotate[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-sched.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-sched.txt deleted file mode 100644 index 8ff4df95..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-sched.txt +++ /dev/null @@ -1,55 +0,0 @@ -perf-sched(1) -============== - -NAME ----- -perf-sched - Tool to trace/measure scheduler properties (latencies) - -SYNOPSIS --------- -[verse] -'perf sched' {record|latency|map|replay|script} - -DESCRIPTION ------------ -There are five variants of perf sched: - - 'perf sched record ' to record the scheduling events - of an arbitrary workload. - - 'perf sched latency' to report the per task scheduling latencies - and other scheduling properties of the workload. - - 'perf sched script' to see a detailed trace of the workload that - was recorded (aliased to 'perf script' for now). - - 'perf sched replay' to simulate the workload that was recorded - via perf sched record. (this is done by starting up mockup threads - that mimic the workload based on the events in the trace. These - threads can then replay the timings (CPU runtime and sleep patterns) - of the workload as it occurred when it was recorded - and can repeat - it a number of times, measuring its performance.) - - 'perf sched map' to print a textual context-switching outline of - workload captured via perf sched record. Columns stand for - individual CPUs, and the two-letter shortcuts stand for tasks that - are running on a CPU. A '*' denotes the CPU that had the event, and - a dot signals an idle CPU. - -OPTIONS -------- --i:: ---input=:: - Input file name. (default: perf.data unless stdin is a fifo) - --v:: ---verbose:: - Be more verbose. (show symbol address, etc) - --D:: ---dump-raw-trace=:: - Display verbose dump of the sched data. - -SEE ALSO --------- -linkperf:perf-record[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-script-perl.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-script-perl.txt deleted file mode 100644 index 3152cca1..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-script-perl.txt +++ /dev/null @@ -1,216 +0,0 @@ -perf-script-perl(1) -================== - -NAME ----- -perf-script-perl - Process trace data with a Perl script - -SYNOPSIS --------- -[verse] -'perf script' [-s [Perl]:script[.pl] ] - -DESCRIPTION ------------ - -This perf script option is used to process perf script data using perf's -built-in Perl interpreter. It reads and processes the input file and -displays the results of the trace analysis implemented in the given -Perl script, if any. - -STARTER SCRIPTS ---------------- - -You can avoid reading the rest of this document by running 'perf script --g perl' in the same directory as an existing perf.data trace file. -That will generate a starter script containing a handler for each of -the event types in the trace file; it simply prints every available -field for each event in the trace file. - -You can also look at the existing scripts in -~/libexec/perf-core/scripts/perl for typical examples showing how to -do basic things like aggregate event data, print results, etc. Also, -the check-perf-script.pl script, while not interesting for its results, -attempts to exercise all of the main scripting features. - -EVENT HANDLERS --------------- - -When perf script is invoked using a trace script, a user-defined -'handler function' is called for each event in the trace. If there's -no handler function defined for a given event type, the event is -ignored (or passed to a 'trace_handled' function, see below) and the -next event is processed. - -Most of the event's field values are passed as arguments to the -handler function; some of the less common ones aren't - those are -available as calls back into the perf executable (see below). - -As an example, the following perf record command can be used to record -all sched_wakeup events in the system: - - # perf record -a -e sched:sched_wakeup - -Traces meant to be processed using a script should be recorded with -the above option: -a to enable system-wide collection. - -The format file for the sched_wakep event defines the following fields -(see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format): - ----- - format: - field:unsigned short common_type; - field:unsigned char common_flags; - field:unsigned char common_preempt_count; - field:int common_pid; - - field:char comm[TASK_COMM_LEN]; - field:pid_t pid; - field:int prio; - field:int success; - field:int target_cpu; ----- - -The handler function for this event would be defined as: - ----- -sub sched::sched_wakeup -{ - my ($event_name, $context, $common_cpu, $common_secs, - $common_nsecs, $common_pid, $common_comm, - $comm, $pid, $prio, $success, $target_cpu) = @_; -} ----- - -The handler function takes the form subsystem::event_name. - -The $common_* arguments in the handler's argument list are the set of -arguments passed to all event handlers; some of the fields correspond -to the common_* fields in the format file, but some are synthesized, -and some of the common_* fields aren't common enough to to be passed -to every event as arguments but are available as library functions. - -Here's a brief description of each of the invariant event args: - - $event_name the name of the event as text - $context an opaque 'cookie' used in calls back into perf - $common_cpu the cpu the event occurred on - $common_secs the secs portion of the event timestamp - $common_nsecs the nsecs portion of the event timestamp - $common_pid the pid of the current task - $common_comm the name of the current process - -All of the remaining fields in the event's format file have -counterparts as handler function arguments of the same name, as can be -seen in the example above. - -The above provides the basics needed to directly access every field of -every event in a trace, which covers 90% of what you need to know to -write a useful trace script. The sections below cover the rest. - -SCRIPT LAYOUT -------------- - -Every perf script Perl script should start by setting up a Perl module -search path and 'use'ing a few support modules (see module -descriptions below): - ----- - use lib "$ENV{'PERF_EXEC_PATH'}/scripts/perl/perf-script-Util/lib"; - use lib "./perf-script-Util/lib"; - use Perf::Trace::Core; - use Perf::Trace::Context; - use Perf::Trace::Util; ----- - -The rest of the script can contain handler functions and support -functions in any order. - -Aside from the event handler functions discussed above, every script -can implement a set of optional functions: - -*trace_begin*, if defined, is called before any event is processed and -gives scripts a chance to do setup tasks: - ----- - sub trace_begin - { - } ----- - -*trace_end*, if defined, is called after all events have been - processed and gives scripts a chance to do end-of-script tasks, such - as display results: - ----- -sub trace_end -{ -} ----- - -*trace_unhandled*, if defined, is called after for any event that - doesn't have a handler explicitly defined for it. The standard set - of common arguments are passed into it: - ----- -sub trace_unhandled -{ - my ($event_name, $context, $common_cpu, $common_secs, - $common_nsecs, $common_pid, $common_comm) = @_; -} ----- - -The remaining sections provide descriptions of each of the available -built-in perf script Perl modules and their associated functions. - -AVAILABLE MODULES AND FUNCTIONS -------------------------------- - -The following sections describe the functions and variables available -via the various Perf::Trace::* Perl modules. To use the functions and -variables from the given module, add the corresponding 'use -Perf::Trace::XXX' line to your perf script script. - -Perf::Trace::Core Module -~~~~~~~~~~~~~~~~~~~~~~~~ - -These functions provide some essential functions to user scripts. - -The *flag_str* and *symbol_str* functions provide human-readable -strings for flag and symbolic fields. These correspond to the strings -and values parsed from the 'print fmt' fields of the event format -files: - - flag_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the flag field $field_name of event $event_name - symbol_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the symbolic field $field_name of event $event_name - -Perf::Trace::Context Module -~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Some of the 'common' fields in the event format file aren't all that -common, but need to be made accessible to user scripts nonetheless. - -Perf::Trace::Context defines a set of functions that can be used to -access this data in the context of the current event. Each of these -functions expects a $context variable, which is the same as the -$context variable passed into every event handler as the second -argument. - - common_pc($context) - returns common_preempt count for the current event - common_flags($context) - returns common_flags for the current event - common_lock_depth($context) - returns common_lock_depth for the current event - -Perf::Trace::Util Module -~~~~~~~~~~~~~~~~~~~~~~~~ - -Various utility functions for use with perf script: - - nsecs($secs, $nsecs) - returns total nsecs given secs/nsecs pair - nsecs_secs($nsecs) - returns whole secs portion given nsecs - nsecs_nsecs($nsecs) - returns nsecs remainder given nsecs - nsecs_str($nsecs) - returns printable string in the form secs.nsecs - avg($total, $n) - returns average given a sum and a total number of values - -SEE ALSO --------- -linkperf:perf-script[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-script-python.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-script-python.txt deleted file mode 100644 index 47102206..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-script-python.txt +++ /dev/null @@ -1,622 +0,0 @@ -perf-script-python(1) -==================== - -NAME ----- -perf-script-python - Process trace data with a Python script - -SYNOPSIS --------- -[verse] -'perf script' [-s [Python]:script[.py] ] - -DESCRIPTION ------------ - -This perf script option is used to process perf script data using perf's -built-in Python interpreter. It reads and processes the input file and -displays the results of the trace analysis implemented in the given -Python script, if any. - -A QUICK EXAMPLE ---------------- - -This section shows the process, start to finish, of creating a working -Python script that aggregates and extracts useful information from a -raw perf script stream. You can avoid reading the rest of this -document if an example is enough for you; the rest of the document -provides more details on each step and lists the library functions -available to script writers. - -This example actually details the steps that were used to create the -'syscall-counts' script you see when you list the available perf script -scripts via 'perf script -l'. As such, this script also shows how to -integrate your script into the list of general-purpose 'perf script' -scripts listed by that command. - -The syscall-counts script is a simple script, but demonstrates all the -basic ideas necessary to create a useful script. Here's an example -of its output (syscall names are not yet supported, they will appear -as numbers): - ----- -syscall events: - -event count ----------------------------------------- ----------- -sys_write 455067 -sys_getdents 4072 -sys_close 3037 -sys_swapoff 1769 -sys_read 923 -sys_sched_setparam 826 -sys_open 331 -sys_newfstat 326 -sys_mmap 217 -sys_munmap 216 -sys_futex 141 -sys_select 102 -sys_poll 84 -sys_setitimer 12 -sys_writev 8 -15 8 -sys_lseek 7 -sys_rt_sigprocmask 6 -sys_wait4 3 -sys_ioctl 3 -sys_set_robust_list 1 -sys_exit 1 -56 1 -sys_access 1 ----- - -Basically our task is to keep a per-syscall tally that gets updated -every time a system call occurs in the system. Our script will do -that, but first we need to record the data that will be processed by -that script. Theoretically, there are a couple of ways we could do -that: - -- we could enable every event under the tracing/events/syscalls - directory, but this is over 600 syscalls, well beyond the number - allowable by perf. These individual syscall events will however be - useful if we want to later use the guidance we get from the - general-purpose scripts to drill down and get more detail about - individual syscalls of interest. - -- we can enable the sys_enter and/or sys_exit syscalls found under - tracing/events/raw_syscalls. These are called for all syscalls; the - 'id' field can be used to distinguish between individual syscall - numbers. - -For this script, we only need to know that a syscall was entered; we -don't care how it exited, so we'll use 'perf record' to record only -the sys_enter events: - ----- -# perf record -a -e raw_syscalls:sys_enter - -^C[ perf record: Woken up 1 times to write data ] -[ perf record: Captured and wrote 56.545 MB perf.data (~2470503 samples) ] ----- - -The options basically say to collect data for every syscall event -system-wide and multiplex the per-cpu output into a single stream. -That single stream will be recorded in a file in the current directory -called perf.data. - -Once we have a perf.data file containing our data, we can use the -g -'perf script' option to generate a Python script that will contain a -callback handler for each event type found in the perf.data trace -stream (for more details, see the STARTER SCRIPTS section). - ----- -# perf script -g python -generated Python script: perf-script.py - -The output file created also in the current directory is named -perf-script.py. Here's the file in its entirety: - -# perf script event handlers, generated by perf script -g python -# Licensed under the terms of the GNU GPL License version 2 - -# The common_* event handler fields are the most useful fields common to -# all events. They don't necessarily correspond to the 'common_*' fields -# in the format files. Those fields not available as handler params can -# be retrieved using Python functions of the form common_*(context). -# See the perf-script-python Documentation for the list of available functions. - -import os -import sys - -sys.path.append(os.environ['PERF_EXEC_PATH'] + \ - '/scripts/python/perf-script-Util/lib/Perf/Trace') - -from perf_trace_context import * -from Core import * - -def trace_begin(): - print "in trace_begin" - -def trace_end(): - print "in trace_end" - -def raw_syscalls__sys_enter(event_name, context, common_cpu, - common_secs, common_nsecs, common_pid, common_comm, - id, args): - print_header(event_name, common_cpu, common_secs, common_nsecs, - common_pid, common_comm) - - print "id=%d, args=%s\n" % \ - (id, args), - -def trace_unhandled(event_name, context, common_cpu, common_secs, common_nsecs, - common_pid, common_comm): - print_header(event_name, common_cpu, common_secs, common_nsecs, - common_pid, common_comm) - -def print_header(event_name, cpu, secs, nsecs, pid, comm): - print "%-20s %5u %05u.%09u %8u %-20s " % \ - (event_name, cpu, secs, nsecs, pid, comm), ----- - -At the top is a comment block followed by some import statements and a -path append which every perf script script should include. - -Following that are a couple generated functions, trace_begin() and -trace_end(), which are called at the beginning and the end of the -script respectively (for more details, see the SCRIPT_LAYOUT section -below). - -Following those are the 'event handler' functions generated one for -every event in the 'perf record' output. The handler functions take -the form subsystem__event_name, and contain named parameters, one for -each field in the event; in this case, there's only one event, -raw_syscalls__sys_enter(). (see the EVENT HANDLERS section below for -more info on event handlers). - -The final couple of functions are, like the begin and end functions, -generated for every script. The first, trace_unhandled(), is called -every time the script finds an event in the perf.data file that -doesn't correspond to any event handler in the script. This could -mean either that the record step recorded event types that it wasn't -really interested in, or the script was run against a trace file that -doesn't correspond to the script. - -The script generated by -g option simply prints a line for each -event found in the trace stream i.e. it basically just dumps the event -and its parameter values to stdout. The print_header() function is -simply a utility function used for that purpose. Let's rename the -script and run it to see the default output: - ----- -# mv perf-script.py syscall-counts.py -# perf script -s syscall-counts.py - -raw_syscalls__sys_enter 1 00840.847582083 7506 perf id=1, args= -raw_syscalls__sys_enter 1 00840.847595764 7506 perf id=1, args= -raw_syscalls__sys_enter 1 00840.847620860 7506 perf id=1, args= -raw_syscalls__sys_enter 1 00840.847710478 6533 npviewer.bin id=78, args= -raw_syscalls__sys_enter 1 00840.847719204 6533 npviewer.bin id=142, args= -raw_syscalls__sys_enter 1 00840.847755445 6533 npviewer.bin id=3, args= -raw_syscalls__sys_enter 1 00840.847775601 6533 npviewer.bin id=3, args= -raw_syscalls__sys_enter 1 00840.847781820 6533 npviewer.bin id=3, args= -. -. -. ----- - -Of course, for this script, we're not interested in printing every -trace event, but rather aggregating it in a useful way. So we'll get -rid of everything to do with printing as well as the trace_begin() and -trace_unhandled() functions, which we won't be using. That leaves us -with this minimalistic skeleton: - ----- -import os -import sys - -sys.path.append(os.environ['PERF_EXEC_PATH'] + \ - '/scripts/python/perf-script-Util/lib/Perf/Trace') - -from perf_trace_context import * -from Core import * - -def trace_end(): - print "in trace_end" - -def raw_syscalls__sys_enter(event_name, context, common_cpu, - common_secs, common_nsecs, common_pid, common_comm, - id, args): ----- - -In trace_end(), we'll simply print the results, but first we need to -generate some results to print. To do that we need to have our -sys_enter() handler do the necessary tallying until all events have -been counted. A hash table indexed by syscall id is a good way to -store that information; every time the sys_enter() handler is called, -we simply increment a count associated with that hash entry indexed by -that syscall id: - ----- - syscalls = autodict() - - try: - syscalls[id] += 1 - except TypeError: - syscalls[id] = 1 ----- - -The syscalls 'autodict' object is a special kind of Python dictionary -(implemented in Core.py) that implements Perl's 'autovivifying' hashes -in Python i.e. with autovivifying hashes, you can assign nested hash -values without having to go to the trouble of creating intermediate -levels if they don't exist e.g syscalls[comm][pid][id] = 1 will create -the intermediate hash levels and finally assign the value 1 to the -hash entry for 'id' (because the value being assigned isn't a hash -object itself, the initial value is assigned in the TypeError -exception. Well, there may be a better way to do this in Python but -that's what works for now). - -Putting that code into the raw_syscalls__sys_enter() handler, we -effectively end up with a single-level dictionary keyed on syscall id -and having the counts we've tallied as values. - -The print_syscall_totals() function iterates over the entries in the -dictionary and displays a line for each entry containing the syscall -name (the dictonary keys contain the syscall ids, which are passed to -the Util function syscall_name(), which translates the raw syscall -numbers to the corresponding syscall name strings). The output is -displayed after all the events in the trace have been processed, by -calling the print_syscall_totals() function from the trace_end() -handler called at the end of script processing. - -The final script producing the output shown above is shown in its -entirety below (syscall_name() helper is not yet available, you can -only deal with id's for now): - ----- -import os -import sys - -sys.path.append(os.environ['PERF_EXEC_PATH'] + \ - '/scripts/python/perf-script-Util/lib/Perf/Trace') - -from perf_trace_context import * -from Core import * -from Util import * - -syscalls = autodict() - -def trace_end(): - print_syscall_totals() - -def raw_syscalls__sys_enter(event_name, context, common_cpu, - common_secs, common_nsecs, common_pid, common_comm, - id, args): - try: - syscalls[id] += 1 - except TypeError: - syscalls[id] = 1 - -def print_syscall_totals(): - if for_comm is not None: - print "\nsyscall events for %s:\n\n" % (for_comm), - else: - print "\nsyscall events:\n\n", - - print "%-40s %10s\n" % ("event", "count"), - print "%-40s %10s\n" % ("----------------------------------------", \ - "-----------"), - - for id, val in sorted(syscalls.iteritems(), key = lambda(k, v): (v, k), \ - reverse = True): - print "%-40s %10d\n" % (syscall_name(id), val), ----- - -The script can be run just as before: - - # perf script -s syscall-counts.py - -So those are the essential steps in writing and running a script. The -process can be generalized to any tracepoint or set of tracepoints -you're interested in - basically find the tracepoint(s) you're -interested in by looking at the list of available events shown by -'perf list' and/or look in /sys/kernel/debug/tracing events for -detailed event and field info, record the corresponding trace data -using 'perf record', passing it the list of interesting events, -generate a skeleton script using 'perf script -g python' and modify the -code to aggregate and display it for your particular needs. - -After you've done that you may end up with a general-purpose script -that you want to keep around and have available for future use. By -writing a couple of very simple shell scripts and putting them in the -right place, you can have your script listed alongside the other -scripts listed by the 'perf script -l' command e.g.: - ----- -root@tropicana:~# perf script -l -List of available trace scripts: - workqueue-stats workqueue stats (ins/exe/create/destroy) - wakeup-latency system-wide min/max/avg wakeup latency - rw-by-file r/w activity for a program, by file - rw-by-pid system-wide r/w activity ----- - -A nice side effect of doing this is that you also then capture the -probably lengthy 'perf record' command needed to record the events for -the script. - -To have the script appear as a 'built-in' script, you write two simple -scripts, one for recording and one for 'reporting'. - -The 'record' script is a shell script with the same base name as your -script, but with -record appended. The shell script should be put -into the perf/scripts/python/bin directory in the kernel source tree. -In that script, you write the 'perf record' command-line needed for -your script: - ----- -# cat kernel-source/tools/perf/scripts/python/bin/syscall-counts-record - -#!/bin/bash -perf record -a -e raw_syscalls:sys_enter ----- - -The 'report' script is also a shell script with the same base name as -your script, but with -report appended. It should also be located in -the perf/scripts/python/bin directory. In that script, you write the -'perf script -s' command-line needed for running your script: - ----- -# cat kernel-source/tools/perf/scripts/python/bin/syscall-counts-report - -#!/bin/bash -# description: system-wide syscall counts -perf script -s ~/libexec/perf-core/scripts/python/syscall-counts.py ----- - -Note that the location of the Python script given in the shell script -is in the libexec/perf-core/scripts/python directory - this is where -the script will be copied by 'make install' when you install perf. -For the installation to install your script there, your script needs -to be located in the perf/scripts/python directory in the kernel -source tree: - ----- -# ls -al kernel-source/tools/perf/scripts/python - -root@tropicana:/home/trz/src/tip# ls -al tools/perf/scripts/python -total 32 -drwxr-xr-x 4 trz trz 4096 2010-01-26 22:30 . -drwxr-xr-x 4 trz trz 4096 2010-01-26 22:29 .. -drwxr-xr-x 2 trz trz 4096 2010-01-26 22:29 bin --rw-r--r-- 1 trz trz 2548 2010-01-26 22:29 check-perf-script.py -drwxr-xr-x 3 trz trz 4096 2010-01-26 22:49 perf-script-Util --rw-r--r-- 1 trz trz 1462 2010-01-26 22:30 syscall-counts.py ----- - -Once you've done that (don't forget to do a new 'make install', -otherwise your script won't show up at run-time), 'perf script -l' -should show a new entry for your script: - ----- -root@tropicana:~# perf script -l -List of available trace scripts: - workqueue-stats workqueue stats (ins/exe/create/destroy) - wakeup-latency system-wide min/max/avg wakeup latency - rw-by-file r/w activity for a program, by file - rw-by-pid system-wide r/w activity - syscall-counts system-wide syscall counts ----- - -You can now perform the record step via 'perf script record': - - # perf script record syscall-counts - -and display the output using 'perf script report': - - # perf script report syscall-counts - -STARTER SCRIPTS ---------------- - -You can quickly get started writing a script for a particular set of -trace data by generating a skeleton script using 'perf script -g -python' in the same directory as an existing perf.data trace file. -That will generate a starter script containing a handler for each of -the event types in the trace file; it simply prints every available -field for each event in the trace file. - -You can also look at the existing scripts in -~/libexec/perf-core/scripts/python for typical examples showing how to -do basic things like aggregate event data, print results, etc. Also, -the check-perf-script.py script, while not interesting for its results, -attempts to exercise all of the main scripting features. - -EVENT HANDLERS --------------- - -When perf script is invoked using a trace script, a user-defined -'handler function' is called for each event in the trace. If there's -no handler function defined for a given event type, the event is -ignored (or passed to a 'trace_handled' function, see below) and the -next event is processed. - -Most of the event's field values are passed as arguments to the -handler function; some of the less common ones aren't - those are -available as calls back into the perf executable (see below). - -As an example, the following perf record command can be used to record -all sched_wakeup events in the system: - - # perf record -a -e sched:sched_wakeup - -Traces meant to be processed using a script should be recorded with -the above option: -a to enable system-wide collection. - -The format file for the sched_wakep event defines the following fields -(see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format): - ----- - format: - field:unsigned short common_type; - field:unsigned char common_flags; - field:unsigned char common_preempt_count; - field:int common_pid; - - field:char comm[TASK_COMM_LEN]; - field:pid_t pid; - field:int prio; - field:int success; - field:int target_cpu; ----- - -The handler function for this event would be defined as: - ----- -def sched__sched_wakeup(event_name, context, common_cpu, common_secs, - common_nsecs, common_pid, common_comm, - comm, pid, prio, success, target_cpu): - pass ----- - -The handler function takes the form subsystem__event_name. - -The common_* arguments in the handler's argument list are the set of -arguments passed to all event handlers; some of the fields correspond -to the common_* fields in the format file, but some are synthesized, -and some of the common_* fields aren't common enough to to be passed -to every event as arguments but are available as library functions. - -Here's a brief description of each of the invariant event args: - - event_name the name of the event as text - context an opaque 'cookie' used in calls back into perf - common_cpu the cpu the event occurred on - common_secs the secs portion of the event timestamp - common_nsecs the nsecs portion of the event timestamp - common_pid the pid of the current task - common_comm the name of the current process - -All of the remaining fields in the event's format file have -counterparts as handler function arguments of the same name, as can be -seen in the example above. - -The above provides the basics needed to directly access every field of -every event in a trace, which covers 90% of what you need to know to -write a useful trace script. The sections below cover the rest. - -SCRIPT LAYOUT -------------- - -Every perf script Python script should start by setting up a Python -module search path and 'import'ing a few support modules (see module -descriptions below): - ----- - import os - import sys - - sys.path.append(os.environ['PERF_EXEC_PATH'] + \ - '/scripts/python/perf-script-Util/lib/Perf/Trace') - - from perf_trace_context import * - from Core import * ----- - -The rest of the script can contain handler functions and support -functions in any order. - -Aside from the event handler functions discussed above, every script -can implement a set of optional functions: - -*trace_begin*, if defined, is called before any event is processed and -gives scripts a chance to do setup tasks: - ----- -def trace_begin: - pass ----- - -*trace_end*, if defined, is called after all events have been - processed and gives scripts a chance to do end-of-script tasks, such - as display results: - ----- -def trace_end: - pass ----- - -*trace_unhandled*, if defined, is called after for any event that - doesn't have a handler explicitly defined for it. The standard set - of common arguments are passed into it: - ----- -def trace_unhandled(event_name, context, common_cpu, common_secs, - common_nsecs, common_pid, common_comm): - pass ----- - -The remaining sections provide descriptions of each of the available -built-in perf script Python modules and their associated functions. - -AVAILABLE MODULES AND FUNCTIONS -------------------------------- - -The following sections describe the functions and variables available -via the various perf script Python modules. To use the functions and -variables from the given module, add the corresponding 'from XXXX -import' line to your perf script script. - -Core.py Module -~~~~~~~~~~~~~~ - -These functions provide some essential functions to user scripts. - -The *flag_str* and *symbol_str* functions provide human-readable -strings for flag and symbolic fields. These correspond to the strings -and values parsed from the 'print fmt' fields of the event format -files: - - flag_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the flag field field_name of event event_name - symbol_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the symbolic field field_name of event event_name - -The *autodict* function returns a special kind of Python -dictionary that implements Perl's 'autovivifying' hashes in Python -i.e. with autovivifying hashes, you can assign nested hash values -without having to go to the trouble of creating intermediate levels if -they don't exist. - - autodict() - returns an autovivifying dictionary instance - - -perf_trace_context Module -~~~~~~~~~~~~~~~~~~~~~~~~~ - -Some of the 'common' fields in the event format file aren't all that -common, but need to be made accessible to user scripts nonetheless. - -perf_trace_context defines a set of functions that can be used to -access this data in the context of the current event. Each of these -functions expects a context variable, which is the same as the -context variable passed into every event handler as the second -argument. - - common_pc(context) - returns common_preempt count for the current event - common_flags(context) - returns common_flags for the current event - common_lock_depth(context) - returns common_lock_depth for the current event - -Util.py Module -~~~~~~~~~~~~~~ - -Various utility functions for use with perf script: - - nsecs(secs, nsecs) - returns total nsecs given secs/nsecs pair - nsecs_secs(nsecs) - returns whole secs portion given nsecs - nsecs_nsecs(nsecs) - returns nsecs remainder given nsecs - nsecs_str(nsecs) - returns printable string in the form secs.nsecs - avg(total, n) - returns average given a sum and a total number of values - -SEE ALSO --------- -linkperf:perf-script[1] diff --git a/ANDROID_3.4.5/tools/perf/Documentation/perf-script.txt b/ANDROID_3.4.5/tools/perf/Documentation/perf-script.txt deleted file mode 100644 index e9cbfcdd..00000000 --- a/ANDROID_3.4.5/tools/perf/Documentation/perf-script.txt +++ /dev/null @@ -1,209 +0,0 @@ -perf-script(1) -============= - -NAME ----- -perf-script - Read perf.data (created by perf record) and display trace output - -SYNOPSIS --------- -[verse] -'perf script' [] -'perf script' [] record