| /external/linux-tools-perf/ |
| D | command-list.txt | 2 # List of known perf commands.
5 perf-annotate mainporcelain common
6 perf-archive mainporcelain common
7 perf-bench mainporcelain common
8 perf-buildid-cache mainporcelain common
9 perf-buildid-list mainporcelain common
10 perf-diff mainporcelain common
11 perf-evlist mainporcelain common
12 perf-inject mainporcelain common
13 perf-list mainporcelain common
[all …]
|
| D | android.patch | 1 diff -r -u -d /home/bccheng/local/kernels/crespo-ics/tools/perf/arch/arm/util/dwarf-regs.c ./arch/a…
2 --- /home/bccheng/local/kernels/crespo-ics/tools/perf/arch/arm/util/dwarf-regs.c 2011-12-09 13:14:4…
29 diff -r -u -d /home/bccheng/local/kernels/crespo-ics/tools/perf/arch/x86/util/dwarf-regs.c ./arch/x…
30 --- /home/bccheng/local/kernels/crespo-ics/tools/perf/arch/x86/util/dwarf-regs.c 2011-12-09 13:14:4…
46 diff -r -u -d /home/bccheng/local/kernels/crespo-ics/tools/perf/bench/mem-memcpy.c ./bench/mem-memc…
47 --- /home/bccheng/local/kernels/crespo-ics/tools/perf/bench/mem-memcpy.c 2011-12-09 13:14:50.000000…
61 diff -r -u -d /home/bccheng/local/kernels/crespo-ics/tools/perf/bench/sched-messaging.c ./bench/sch…
62 --- /home/bccheng/local/kernels/crespo-ics/tools/perf/bench/sched-messaging.c 2011-12-09 13:14:50.0…
76 diff -r -u -d /home/bccheng/local/kernels/crespo-ics/tools/perf/bench/sched-pipe.c ./bench/sched-pi…
77 --- /home/bccheng/local/kernels/crespo-ics/tools/perf/bench/sched-pipe.c 2011-12-09 13:14:50.000000…
[all …]
|
| /external/linux-tools-perf/Documentation/ |
| D | perf-kvm.txt | 1 perf-kvm(1)
6 perf-kvm - Tool to trace/measure kvm guest os
11 'perf kvm' [--host] [--guest] [--guestmount=<path>
14 'perf kvm' [--host] [--guest] [--guestkallsyms=<path> --guestmodules=<path>
19 There are a couple of variants of perf kvm:
21 'perf kvm [options] top <command>' to generates and displays
25 'perf kvm record <command>' to record the performance counter profile
26 of an arbitrary workload and save it into a perf data file. If both
27 --host and --guest are input, the perf data file name is perf.data.kvm.
28 If there is no --host but --guest, the file name is perf.data.guest.
[all …]
|
| D | perf-evlist.txt | 1 perf-evlist(1)
6 perf-evlist - List the event names in a perf.data file
11 'perf evlist <options>'
15 This command displays the names of events sampled in a perf.data file.
21 Input file name. (default: perf.data)
25 linkperf:perf-record[1], linkperf:perf-list[1],
26 linkperf:perf-report[1]
|
| D | perf-buildid-list.txt | 1 perf-buildid-list(1)
6 perf-buildid-list - List the buildids in a perf.data file
11 'perf buildid-list <options>'
15 This command displays the buildids found in a perf.data file, so that other
17 perf report.
26 Input file name. (default: perf.data)
36 linkperf:perf-record[1], linkperf:perf-top[1],
37 linkperf:perf-report[1]
|
| D | perf-archive.txt | 1 perf-archive(1)
6 perf-archive - Create archive with object files with build-ids found in perf.data file
11 'perf archive' [file]
15 This command runs runs perf-buildid-list --with-hits, and collects the files
16 with the buildids found so that analisys of perf.data contents can be possible
22 linkperf:perf-record[1], linkperf:perf-buildid-list[1], linkperf:perf-report[1]
|
| D | perf-script.txt | 1 perf-script(1)
6 perf-script - Read perf.data (created by perf record) and display trace output
11 'perf script' [<options>]
12 'perf script' [<options>] record <script> [<record-options>] <command>
13 'perf script' [<options>] report <script> [script-args]
14 'perf script' [<options>] <script> <required-script-args> [<record-options>] <command>
15 'perf script' [<options>] <top-script> [script-args]
21 There are several variants of perf script:
23 'perf script' to see a detailed trace of the workload that was
28 available via 'perf script -l'). The following variants allow you to
[all …]
|
| D | perf-sched.txt | 1 perf-sched(1)
6 perf-sched - Tool to trace/measure scheduler properties (latencies)
11 'perf sched' {record|latency|map|replay|trace}
15 There are five variants of perf sched:
17 'perf sched record <command>' to record the scheduling events
20 'perf sched latency' to report the per task scheduling latencies
23 'perf sched trace' to see a detailed trace of the workload that
26 'perf sched replay' to simulate the workload that was recorded
27 via perf sched record. (this is done by starting up mockup threads
33 'perf sched map' to print a textual context-switching outline of
[all …]
|
| D | perf.txt | 1 perf(1)
6 perf - Performance analysis tools for Linux
11 'perf' [--version] [--help] COMMAND [ARGS]
22 linkperf:perf-stat[1], linkperf:perf-top[1],
23 linkperf:perf-record[1], linkperf:perf-report[1],
24 linkperf:perf-list[1]
|
| D | perf-help.txt | 1 perf-help(1)
6 perf-help - display help information about perf
10 'perf help' [-a|--all] [COMMAND]
15 With no options and no COMMAND given, the synopsis of the 'perf'
16 command and a list of the most commonly used perf commands are printed
22 If a perf command is named, a manual page for that command is brought
26 Note that `perf --help ...` is identical to `perf help ...` because the
38 Part of the linkperf:perf[1] suite
|
| D | perf-lock.txt | 1 perf-lock(1)
6 perf-lock - Analyze lock events
11 'perf lock' {record|report|trace}
16 and statistics with this 'perf lock' command.
18 'perf lock record <command>' records lock events
20 produces the file "perf.data" which contains tracing
23 'perf lock trace' shows raw lock events.
25 'perf lock report' reports statistical data.
52 linkperf:perf[1]
|
| D | perf-inject.txt | 1 perf-inject(1)
6 perf-inject - Filter to augment the events stream with additional information
11 'perf inject <options>'
15 perf-inject reads a perf-record event stream and repipes it to stdout. At any
20 Build-ids are just the first user of perf-inject - potentially anything that
35 linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1]
|
| D | perf-kmem.txt | 1 perf-kmem(1)
6 perf-kmem - Tool to trace/measure kernel memory(slab) properties
11 'perf kmem' {record|stat} [<options>]
15 There are two variants of perf kmem:
17 'perf kmem record <command>' to record the kmem events
20 'perf kmem stat' to report kernel memory statistics.
26 Select the input file (default: perf.data)
47 linkperf:perf-record[1]
|
| D | perf-script-python.txt | 1 perf-script-python(1)
6 perf-script-python - Process trace data with a Python script
11 'perf script' [-s [Python]:script[.py] ]
16 This perf script option is used to process perf script data using perf's
26 raw perf script stream. You can avoid reading the rest of this
32 'syscall-counts' script you see when you list the available perf script
33 scripts via 'perf script -l'. As such, this script also shows how to
34 integrate your script into the list of general-purpose 'perf script'
81 allowable by perf. These individual syscall events will however be
92 don't care how it exited, so we'll use 'perf record' to record only
[all …]
|
| D | perf-bench.txt | 1 perf-bench(1)
6 perf-bench - General framework for benchmark suites
11 'perf bench' [<common options>] <subsystem> <suite> [<options>]
15 This 'perf bench' command is general framework for benchmark suites.
27 % perf bench sched pipe # with no style specified
38 % perf bench --format=simple sched pipe # specified simple
76 % perf bench sched messaging # run with default
82 % perf bench sched messaging -t -g 20 # be multi-thread, with 20 groups
103 % perf bench sched pipe
110 % perf bench sched pipe -l 1000 # loop 1000
[all …]
|
| D | perf-timechart.txt | 1 perf-timechart(1)
6 perf-timechart - Tool to visualize total system behavior during a workload
11 'perf timechart' {record}
15 There are two variants of perf timechart:
17 'perf timechart record <command>' to record the system level events
20 'perf timechart' to turn a trace into a Scalable Vector Graphics file,
30 Select the input file (default: perf.data)
46 linkperf:perf-record[1]
|
| D | perf-diff.txt | 1 perf-diff(1)
6 perf-diff - Read two perf.data files and display the differential profile
11 'perf diff' [oldfile] [newfile]
15 This command displays the performance difference amongst two perf.data files
16 captured via perf record.
18 If no parameters are passed it will assume perf.data.old and perf.data.
74 linkperf:perf-record[1]
|
| D | perf-buildid-cache.txt | 1 perf-buildid-cache(1)
6 perf-buildid-cache - Manage build-id cache.
11 'perf buildid-cache <options>'
33 linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-buildid-list[1]
|
| D | examples.txt | 3 ****** perf by examples ******
10 'perf list':
12 titan:~> perf list
31 titan:~> perf stat -e kmem:mm_page_pcpu_drain -e kmem:mm_page_alloc
45 'repeat the workload N times' feature of perf stat:
47 titan:~> perf stat --repeat 5 -e kmem:mm_page_pcpu_drain -e
69 titan:~/git> perf record -f -e kmem:mm_page_alloc -c 1 ./git gc
75 [ perf record: Captured and wrote 0.267 MB perf.data (~11679 samples) ]
79 titan:~/git> perf report
99 0.68% perf /lib64/libpthread-2.5.so
[all …]
|
| D | perf-annotate.txt | 1 perf-annotate(1)
6 perf-annotate - Read perf.data (created by perf record) and display annotated code
11 'perf annotate' [-i <file> | --input=file] [symbol_name]
25 Input file name. (default: perf.data)
71 linkperf:perf-record[1], linkperf:perf-report[1]
|
| /external/chromium_org/tools/perf/ |
| D | bootstrap_deps | 5 # This file specifies dependencies required to bootstrap tools/perf. It is in a
7 # but it should only be used to bootstrap tools/perf *outside* of a normal
11 "src/tools/perf/benchmarks":
12 "https://src.chromium.org/chrome/trunk/src/tools/perf/benchmarks",
13 "src/tools/perf/measurements":
14 "https://src.chromium.org/chrome/trunk/src/tools/perf/measurements",
15 "src/tools/perf/page_sets":
16 "https://src.chromium.org/chrome/trunk/src/tools/perf/page_sets",
17 "src/tools/perf/metrics":
18 "https://src.chromium.org/chrome/trunk/src/tools/perf/metrics",
[all …]
|
| /external/linux-tools-perf/python/ |
| D | twatch.py | 16 import perf
19 cpus = perf.cpu_map()
20 threads = perf.thread_map()
21 evsel = perf.evsel(task = 1, comm = 1, mmap = 0,
24 sample_type = perf.SAMPLE_PERIOD | perf.SAMPLE_TID | perf.SAMPLE_CPU | perf.SAMPLE_TID)
26 evlist = perf.evlist(cpus, threads)
|
| /external/chromium_org/chrome/test/functional/ |
| D | PYAUTO_TESTS | 287 'perf',
292 '-perf.HTML5BenchmarkTest', # crbug.com/134476
293 '-perf.LiveWebappLoadTest.testNewTabGmail', # crbug.com/136554
294 '-perf.ScrollTest.testGmailScroll', # crbug.com/136554
295 '-perf.WebGLTest.testWebGLField', # crbug.com/132797
301 '-perf.BenchmarkPerfTest.testSpaceport',
302 '-perf.PopularSitesScrollTest.test2012Q3',
308 '-perf.GPUPerfTest', # Fails. Discuss with prachij@.
309 '-perf.PageCyclerNetSimTest', # Dependence missing: crbug.com/132559
310 '-perf.LiveGamePerfTest', # Requires linux /proc/stat.
[all …]
|
| /external/chromium_org/tools/perf_expectations/ |
| D | make_expectations.py | 166 perf = ConvertJsonIntoDict(ReadFile(perf_file))
169 perfkeys = perf.keys()
177 value = perf[key]
185 rowdata = GetRowData(perf, key)
305 if 'regress' in perf[key] and 'improve' in perf[key]:
306 if perf[key]['regress'] < perf[key]['improve']:
316 perf[key]['regress'] == perf[key]['improve'])
341 checksum_rowdata = GetRowData(perf, key)
344 if ('regress' in perf[key] and 'improve' in perf[key] and
345 perf[key]['regress'] == regress and perf[key]['improve'] == improve and
[all …]
|
| /external/icu4c/test/perf/dicttrieperf/ |
| D | dicttrieperf.cpp | 81 PackageLookup(const DictionaryTriePerfTest &perf) { in PackageLookup() argument
83 CharString filename(perf.getSourceDir(), errorCode); in PackageLookup()
137 BinarySearchPackageLookup(const DictionaryTriePerfTest &perf) in BinarySearchPackageLookup() argument
138 : PackageLookup(perf) { in BinarySearchPackageLookup()
246 PrefixBinarySearchPackageLookup(const DictionaryTriePerfTest &perf) in PrefixBinarySearchPackageLookup() argument
247 : BinarySearchPackageLookup(perf) {} in PrefixBinarySearchPackageLookup()
273 BytesTriePackageLookup(const DictionaryTriePerfTest &perf) in BytesTriePackageLookup() argument
274 : PackageLookup(perf) { in BytesTriePackageLookup()
329 DictLookup(const DictionaryTriePerfTest &perfTest) : perf(perfTest) {} in DictLookup()
332 return perf.numTextLines; in getOperationsPerIteration()
[all …]
|