Home
last modified time | relevance | path

Searched full:perf (Results 1 – 25 of 1342) sorted by relevance

12345678910>>...54

/linux/tools/perf/util/
H A DBuild4 perf-util-y += arm64-frame-pointer-unwind-support.o
5 perf-util-y += addr_location.o
6 perf-util-y += annotate.o
7 perf-util-y += block-info.o
8 perf-util-y += block-range.o
9 perf-util-y += build-id.o
10 perf-util-y += cacheline.o
11 perf-util-y += config.o
12 perf-util-y += copyfile.o
13 perf-util-y += ctype.o
[all …]
/linux/tools/perf/tests/
H A DBuild3 perf-test-y += builtin-test.o
4 perf-test-y += tests-scripts.o
5 perf-test-y += parse-events.o
6 perf-test-y += dso-data.o
7 perf-test-y += attr.o
8 perf-test-y += vmlinux-kallsyms.o
9 perf-test-$(CONFIG_LIBTRACEEVENT) += openat-syscall.o
10 perf-test-$(CONFIG_LIBTRACEEVENT) += openat-syscall-all-cpus.o
11 perf-test-$(CONFIG_LIBTRACEEVENT) += openat-syscall-tp-fields.o
12 perf-test-$(CONFIG_LIBTRACEEVENT) += mmap-basic.o
[all …]
H A Dhists_cumulate.c27 /* perf [kernel] schedule() */
29 /* perf [perf] main() */
31 /* perf [perf] cmd_record() */
33 /* perf [libc] malloc() */
35 /* perf [libc] free() */
37 /* perf [perf] main() */
39 /* perf [kerne
[all...]
H A Dhists_common.h43 * perf: 100 perf main
44 * perf: 100 perf run_command
45 * perf: 100 perf cmd_record
46 * perf: 100 libc malloc
47 * perf: 100 libc free
48 * perf: 100 libc realloc
49 * perf: 100 [kernel] schedule
50 * perf: 100 [kernel] page_fault
51 * perf: 100 [kernel] sys_perf_event_open
52 * perf: 200 perf main
[all …]
/linux/tools/perf/Documentation/
H A 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
6 Customize output of perf script with: perf script -F event,ip,sym
7 Generate a script for your data: perf script -g <lang>
8 Save output of perf stat using: perf stat record <target workload>
9 Create an archive with symtabs to analyse on other machine: perf archive
10 Search options using a keyword: perf report -h <keyword>
11 Use parent filter to see specific call path: perf report -p <regex>
[all …]
H A Dperf.txt1 perf(1)
6 perf - Performance analysis tools for Linux
11 'perf' [--version] [--help] [OPTIONS] COMMAND [ARGS]
17 Run perf help command.
21 Display perf version.
44 List the most commonly used perf commands.
47 List available perf options.
64 perf-event-open - Print perf_event_open() arguments and
66 kmaps - Print kernel and module maps (perf script
67 and perf report without browser)
[all …]
H A Dperf-daemon.txt1 perf-daemon(1)
7 perf-daemon - Run record sessions on background
13 'perf daemon'
14 'perf daemon' [<options>]
15 'perf daemon start' [<options>]
16 'perf daemon stop' [<options>]
17 'perf daemon signal' [<options>]
18 'perf daemon ping' [<options>]
26 You can imagine 'perf daemon' of background process with several
27 'perf record' child tasks, like:
[all …]
H A 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 …]
H A 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 …]
H A Dperf-amd-ibs.txt1 perf-amd-ibs(1)
6 perf-amd-ibs - Support for AMD Instruction-Based Sampling (IBS) with perf tool
11 'perf record' -e ibs_op//
12 'perf record' -e ibs_fetch//
27 using the Linux perf utility. The following files will be created at boot time
44 (sample was generated at IP X but perf would record it at IP X+n). Hence,
66 # perf record -e ibs_op// -c 100000 -a
70 # perf record -e ibs_op// -c 100000 -C 10
74 # perf record -e ibs_op// -F 1000 -C 10
78 # perf record -e ibs_op/cnt_ctl=1/ -c 100000 -a
[all …]
H A 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 …]
/linux/tools/perf/
H A 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 …]
H A DBuild1 perf-bench-y += builtin-bench.o
2 perf-y += builtin-annotate.o
3 perf-y += builtin-check.o
4 perf-y += builtin-config.o
5 perf-y += builtin-diff.o
6 perf-y += builtin-evlist.o
7 perf-y += builtin-ftrace.o
8 perf-y += builtin-help.o
9 perf-y += builtin-buildid-list.o
10 perf-y += builtin-buildid-cache.o
[all …]
H A D.gitignore2 PERF-CFLAGS
3 PERF-GUI-VARS
4 PERF-VERSION-FILE
6 perf
7 !include/perf/
8 perf-read-vdso32
9 perf-read-vdsox32
10 perf-help
11 perf-record
12 perf-report
[all …]
/linux/drivers/ntb/test/
H A Dntb_perf.c45 * PCIe NTB Perf Linux driver
126 * Perf driver data definition
144 struct perf_ctx *perf; member
169 struct perf_ctx *perf; member
205 int (*cmd_recv)(struct perf_ctx *perf, int *pidx, enum perf_cmd *cmd,
247 static void perf_terminate_test(struct perf_ctx *perf);
253 link = ntb_link_is_up(peer->perf->ntb, NULL, NULL); in perf_link_is_up()
260 struct perf_ctx *perf = peer->perf; in perf_spad_cmd_send() local
264 dev_dbg(&perf->ntb->dev, "CMD send: %d 0x%llx\n", cmd, data); in perf_spad_cmd_send()
277 sts = ntb_peer_spad_read(perf->ntb, peer->pidx, in perf_spad_cmd_send()
[all …]
/linux/tools/perf/tests/shell/
H A Dtest_task_analyzer.sh2 # perf script task-analyzer tests
5 tmpdir=$(mktemp -d /tmp/perf-script-task-analyzer-XXXXX)
10 if [ -e "$perfdir/scripts/python/Perf-Trace-Util" ]; then
18 rm -f perf.data
19 rm -f perf.data.old
56 # check if perf is compiled with libtraceevent support
58 perf check feature -q libtraceevent && return 0
64 perf record -e sched:sched_switch -a -- sleep 1 > /dev/null 2>&1
65 # check if perf data file got created in above step.
66 if [ ! -e "perf.data" ]; then
[all …]
H A Dlock_contention.sh8 perfdata=$(mktemp /tmp/__perf_test.perf.data.XXXXX)
30 if ! perf list | grep -q lock:contention_begin; then
46 echo "Testing perf lock record and perf lock contention"
47 perf lock record -o ${perfdata} -- perf bench sched messaging > /dev/null 2>&1
49 perf lock contention -i ${perfdata} -E 1 -q 2> ${result}
59 echo "Testing perf lock contention --use-bpf"
61 if ! perf lock con -b true > /dev/null 2>&1 ; then
66 # the perf lock contention output goes to the stderr
67 perf lock con -a -b -E 1 -q -- perf bench sched messaging > /dev/null 2> ${result}
77 echo "Testing perf lock record and perf lock contention at the same time"
[all …]
H A Dpipe_test.sh2 # perf pipe recording and injection test
13 data=$(mktemp /tmp/perf.data.XXXXXX)
14 data2=$(mktemp /tmp/perf.data2.XXXXXX)
15 prog="perf test -w noploop"
40 task="perf"
41 if ! perf record -e task-clock:u -o - ${prog} | perf report -i - --task | grep -q ${task}
43 echo "Record+report pipe test [Failed - cannot find the test file in the perf report #1]"
48 if ! perf record -g -e task-clock:u -o - ${prog} | perf report -i - --task | grep -q ${task}
50 echo "Record+report pipe test [Failed - cannot find the test file in the perf report #2]"
55 perf record -g -e task-clock:u -o - ${prog} > ${data}
[all …]
/linux/drivers/gpu/drm/nouveau/nvkm/subdev/bios/
H A Dperf.c26 #include <subdev/bios/perf.h>
34 u32 perf = 0; in nvbios_perf_table() local
38 perf = nvbios_rd32(bios, bit_P.offset + 0); in nvbios_perf_table()
39 if (perf) { in nvbios_perf_table()
40 *ver = nvbios_rd08(bios, perf + 0); in nvbios_perf_table()
41 *hdr = nvbios_rd08(bios, perf + 1); in nvbios_perf_table()
43 *cnt = nvbios_rd08(bios, perf + 5); in nvbios_perf_table()
44 *len = nvbios_rd08(bios, perf + 2); in nvbios_perf_table()
45 *snr = nvbios_rd08(bios, perf + 4); in nvbios_perf_table()
46 *ssz = nvbios_rd08(bios, perf + 3); in nvbios_perf_table()
[all …]
/linux/tools/perf/tests/attr/
H A 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 …]
/linux/tools/perf/bench/
H A DBuild1 perf-bench-y += sched-messaging.o
2 perf-bench-y += sched-pipe.o
3 perf-bench-y += sched-seccomp-notify.o
4 perf-bench-y += syscall.o
5 perf-bench-y += mem-functions.o
6 perf-bench-y += futex-hash.o
7 perf-bench-y += futex-wake.o
8 perf-bench-y += futex-wake-parallel.o
9 perf-bench-y += futex-requeue.o
10 perf-bench-y += futex-lock-pi.o
[all …]
/linux/tools/perf/arch/x86/util/
H A DBuild1 perf-util-y += header.o
2 perf-util-y += tsc.o
3 perf-util-y += pmu.o
4 perf-util-$(CONFIG_LIBTRACEEVENT) += kvm-stat.o
5 perf-util-y += perf_regs.o
6 perf-util-y += topdown.o
7 perf-util-y += machine.o
8 perf-util-y += event.o
9 perf-util-y += evlist.o
10 perf-util-y += mem-events.o
[all …]
/linux/tools/perf/trace/beauty/
H A DBuild1 perf-y += clone.o
2 perf-y += fcntl.o
3 perf-y += flock.o
4 perf-y += fs_at_flags.o
5 perf-y += fsmount.o
6 perf-y += fspick.o
8 perf-y += ioctl.o
10 perf-y += kcmp.o
11 perf-y += mount_flags.o
12 perf
[all...]
/linux/tools/perf/tests/shell/common/
H A Dpatterns.sh161 export RE_LINE_RECORD1="^\[\s+perf\s+record:\s+Woken up $RE_NUMBER times? to write data\s+\].*$"
162 # The first line of perf-record "OK" output
164 # [ perf record: Woken up 1 times to write data ]
167 export RE_LINE_RECORD2="^\[\s+perf\s+record:\s+Captured and wrote $RE_NUMBER\s*MB\s+(?:[\w\+\.-]*(?…
168 # The second line of perf-record "OK" output
170 # [ perf record: Captured and wrote 0.405 MB perf.data (109 samples) ]
171 # [ perf record: Captured and wrote 0.405 MB perf.data (~109 samples) ]
172 # [ perf record: Captured and wrote 0.405 MB /some/temp/dir/perf.data (109 samples) ]
173 # [ perf record: Captured and wrote 0.405 MB ./perf.data (109 samples) ]
174 # [ perf record: Captured and wrote 0.405 MB ./perf.data.3 (109 samples) ]
[all …]
/linux/Documentation/trace/coresight/
H A Dcoresight-perf.rst4 CoreSight - Perf
10 Perf is able to locally access CoreSight trace data and store it to the
11 output perf data files. This data can then be later decoded to give the
13 can log such data with a perf record command like::
15 perf record -e cs_etm//u testbinary
18 a perf.data trace file. That file would have AUX sections if CoreSight
22 perf report --stdio --dump -i perf.data
43 To compile perf with CoreSight support in the tools/perf directory do::
53 For complete information on building perf with CoreSight support and
81 Perf test - Verify kernel and userspace perf CoreSight work
[all …]

12345678910>>...54