Home
last modified time | relevance | path

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

123456789

/tools/perf/
Dcommand-list.txt2 # 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-data mainporcelain common
11 perf-diff mainporcelain common
12 perf-c2c mainporcelain common
13 perf-config mainporcelain common
[all …]
DBuild1 perf-y += builtin-bench.o
2 perf-y += builtin-annotate.o
3 perf-y += builtin-config.o
4 perf-y += builtin-diff.o
5 perf-y += builtin-evlist.o
6 perf-y += builtin-ftrace.o
7 perf-y += builtin-help.o
8 perf-y += builtin-sched.o
9 perf-y += builtin-buildid-list.o
10 perf-y += builtin-buildid-cache.o
[all …]
D.gitignore6 perf
7 perf-read-vdso32
8 perf-read-vdsox32
9 perf-help
10 perf-record
11 perf-report
12 perf-stat
13 perf-top
14 perf*.1
15 perf*.xml
[all …]
/tools/perf/util/
DBuild1 perf-y += annotate.o
2 perf-y += block-info.o
3 perf-y += block-range.o
4 perf-y += build-id.o
5 perf-y += cacheline.o
6 perf-y += config.o
7 perf-y += copyfile.o
8 perf-y += ctype.o
9 perf-y += db-export.o
10 perf-y += env.o
[all …]
/tools/perf/tests/
DBuild3 perf-y += builtin-test.o
4 perf-y += parse-events.o
5 perf-y += dso-data.o
6 perf-y += attr.o
7 perf-y += vmlinux-kallsyms.o
8 perf-y += openat-syscall.o
9 perf-y += openat-syscall-all-cpus.o
10 perf-y += openat-syscall-tp-fields.o
11 perf-y += mmap-basic.o
12 perf-y += perf-record.o
[all …]
/tools/perf/trace/beauty/
DBuild1 perf-y += clone.o
2 perf-y += fcntl.o
3 perf-y += flock.o
4 perf-y += fsmount.o
5 perf-y += fspick.o
7 perf-y += ioctl.o
9 perf-y += kcmp.o
10 perf-y += mount_flags.o
11 perf-y += move_mount.o
12 perf-y += pkey_alloc.o
[all …]
/tools/perf/bench/
DBuild1 perf-y += sched-messaging.o
2 perf-y += sched-pipe.o
3 perf-y += syscall.o
4 perf-y += mem-functions.o
5 perf-y += futex-hash.o
6 perf-y += futex-wake.o
7 perf-y += futex-wake-parallel.o
8 perf-y += futex-requeue.o
9 perf-y += futex-lock-pi.o
10 perf-y += epoll-wait.o
[all …]
/tools/perf/arch/x86/util/
DBuild1 perf-y += header.o
2 perf-y += tsc.o
3 perf-y += pmu.o
4 perf-y += kvm-stat.o
5 perf-y += perf_regs.o
6 perf-y += topdown.o
7 perf-y += machine.o
8 perf-y += event.o
10 perf-$(CONFIG_DWARF) += dwarf-regs.o
11 perf-$(CONFIG_BPF_PROLOGUE) += dwarf-regs.o
[all …]
/tools/perf/Documentation/
Dtips.txt1 For a higher level overview, try: perf report --sort comm,dso
2 Sample related events with: perf record -e '{cycles,instructions}:S'
3 Compare performance results with: perf diff [<old file> <new file>]
4 Boolean options have negative forms, e.g.: perf report --no-children
5 Customize output of perf script with: perf script -F event,ip,sym
6 Generate a script for your data: perf script -g <lang>
7 Save output of perf stat using: perf stat record <target workload>
8 Create an archive with symtabs to analyse on other machine: perf archive
9 Search options using a keyword: perf report -h <keyword>
10 Use parent filter to see specific call path: perf report -p <regex>
[all …]
Dperf.data-directory-format.txt1 perf.data directory format
4 in following versions of perf. We will remove this
8 This document describes the on-disk perf.data directory format.
20 - there is a single perf.data file named 'data' within the directory.
23 $ tree -ps perf.data
24 perf.data
30 Currently the only 'perf record' option to output to a directory is
34 $ sudo perf record --kcore uname
36 [ perf record: Woken up 1 times to write data ]
37 [ perf record: Captured and wrote 0.015 MB perf.data (9 samples) ]
[all …]
Dperf-archive.txt1 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 perf-buildid-list --with-hits, and collects the files with the
16 buildids found so that analysis of perf.data contents can be possible on another
22 linkperf:perf-record[1], linkperf:perf-buildid-list[1], linkperf:perf-report[1]
DBuild.txt2 1) perf build
4 The perf build process consists of several separated building blocks,
5 which are linked together to form the perf binary:
7 - perf builtin commands
11 Several makefiles govern the perf build:
15 Makefile.perf with a -j option to do parallel builds.
17 - Makefile.perf
18 main makefile that triggers build of all perf objects including
34 2) perf build
36 The Makefile.perf triggers the build framework for build objects:
[all …]
Dperf-kvm.txt1 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>
16 'perf kvm stat [record|report|live] [<options>]
20 There are a couple of variants of perf kvm:
22 'perf kvm [options] top <command>' to generates and displays
26 'perf kvm record <command>' to record the performance counter profile
27 of an arbitrary workload and save it into a perf data file. We set the
28 default behavior of perf kvm as --guest, so if neither --host nor --guest
[all …]
Dperf-evlist.txt1 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 unless stdin is a fifo)
44 linkperf:perf-record[1], linkperf:perf-list[1],
45 linkperf:perf-report[1]
Dperf-lock.txt1 perf-lock(1)
6 perf-lock - Analyze lock events
11 'perf lock' {record|report|script|info}
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 report' reports statistical data.
25 'perf lock script' shows raw lock events.
27 'perf lock info' shows metadata like threads or addresses
35 Input file name. (default: perf.data unless stdin is a fifo)
[all …]
Dperf-buildid-list.txt1 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.
29 Input file name. (default: perf.data unless stdin is a fifo)
42 linkperf:perf-record[1], linkperf:perf-top[1],
43 linkperf:perf-report[1]
/tools/perf/python/
Dtracepoint.py6 import perf
8 class tracepoint(perf.evsel):
10 config = perf.tracepoint(sys, name)
11 perf.evsel.__init__(self,
12 type = perf.TYPE_TRACEPOINT,
15 …sample_type = perf.SAMPLE_PERIOD | perf.SAMPLE_TID | perf.SAMPLE_CPU | perf.SAMPLE_RAW | perf.SAMP…
19 cpus = perf.cpu_map()
20 threads = perf.thread_map(-1)
22 evlist = perf.evlist(cpus, threads)
34 if not isinstance(event, perf.sample_event):
Dtwatch.py9 import perf
12 cpus = perf.cpu_map()
13 threads = perf.thread_map(thread)
14 evsel = perf.evsel(type = perf.TYPE_SOFTWARE,
15 config = perf.COUNT_SW_DUMMY,
19 sample_type = perf.SAMPLE_PERIOD | perf.SAMPLE_TID | perf.SAMPLE_CPU)
29 evlist = perf.evlist(cpus, threads)
/tools/perf/tests/attr/
DREADME3 This testing support is embedded into perf directly and is governed
8 each event created within single perf command. Each event details
9 are stored into separate text file. Once perf command is finished
33 Following tests are defined (with perf commands):
35 perf record kill (test-record-basic)
36 perf record -b kill (test-record-branch-any)
37 perf record -j any kill (test-record-branch-filter-any)
38 perf record -j any_call kill (test-record-branch-filter-any_call)
39 perf record -j any_ret kill (test-record-branch-filter-any_ret)
40 perf record -j hv kill (test-record-branch-filter-hv)
[all …]
/tools/perf/ui/
DBuild1 perf-y += setup.o
2 perf-y += helpline.o
3 perf-y += progress.o
4 perf-y += util.o
5 perf-y += hist.o
6 perf-y += stdio/hist.o
10 perf-$(CONFIG_SLANG) += browser.o
11 perf-$(CONFIG_SLANG) += browsers/
12 perf-$(CONFIG_SLANG) += tui/
/tools/perf/arch/powerpc/util/
DBuild1 perf-y += header.o
2 perf-y += kvm-stat.o
3 perf-y += perf_regs.o
4 perf-y += mem-events.o
5 perf-y += sym-handling.o
7 perf-$(CONFIG_DWARF) += dwarf-regs.o
8 perf-$(CONFIG_DWARF) += skip-callchain-idx.o
10 perf-$(CONFIG_LIBUNWIND) += unwind-libunwind.o
11 perf-$(CONFIG_LIBDW_DWARF_UNWIND) += unwind-libdw.o
/tools/perf/arch/x86/tests/
DBuild1 perf-$(CONFIG_DWARF_UNWIND) += regs_load.o
2 perf-$(CONFIG_DWARF_UNWIND) += dwarf-unwind.o
4 perf-y += arch-tests.o
5 perf-y += rdpmc.o
6 perf-y += perf-time-to-tsc.o
7 perf-$(CONFIG_AUXTRACE) += insn-x86.o intel-pt-pkt-decoder-test.o
8 perf-$(CONFIG_X86_64) += bp-modify.o
/tools/perf/arch/s390/util/
DBuild1 perf-y += header.o
2 perf-y += kvm-stat.o
3 perf-y += perf_regs.o
5 perf-$(CONFIG_DWARF) += dwarf-regs.o
6 perf-$(CONFIG_LIBDW_DWARF_UNWIND) += unwind-libdw.o
8 perf-y += machine.o
10 perf-$(CONFIG_AUXTRACE) += auxtrace.o
/tools/perf/arch/arm64/util/
DBuild1 perf-y += header.o
2 perf-y += perf_regs.o
3 perf-y += tsc.o
4 perf-$(CONFIG_DWARF) += dwarf-regs.o
5 perf-$(CONFIG_LOCAL_LIBUNWIND) += unwind-libunwind.o
6 perf-$(CONFIG_LIBDW_DWARF_UNWIND) += unwind-libdw.o
8 perf-$(CONFIG_AUXTRACE) += ../../arm/util/pmu.o \
/tools/perf/tests/shell/
Dtest_arm_coresight.sh12 perfdata=$(mktemp /tmp/__perf_test.perf.data.XXXXX)
16 perf list | grep -q 'cs_etm//' && return 0
35 perf record -o ${perfdata} -e cs_etm/@$1/u --per-thread \
46 perf script -F,-time -i ${perfdata} | \
57 perf report --stdio -i ${perfdata} | \
68 perf report --itrace=i1000i --stdio -i ${perfdata} | \
142 perf record -o ${perfdata} -e cs_etm// -a -- ls
144 perf_script_branch_samples perf &&
145 perf_report_branch_samples perf &&
146 perf_report_instruction_samples perf
[all …]

123456789