Home
last modified time | relevance | path

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

/linux-4.4.14/drivers/gpu/drm/msm/
Dmsm_perf.c52 static int wait_sample(struct msm_perf_state *perf) in wait_sample() argument
56 if (time_after(perf->next_jiffies, start_jiffies)) { in wait_sample()
58 perf->next_jiffies - start_jiffies; in wait_sample()
65 perf->next_jiffies += SAMPLE_TIME; in wait_sample()
69 static int refill_buf(struct msm_perf_state *perf) in refill_buf() argument
71 struct msm_drm_private *priv = perf->dev->dev_private; in refill_buf()
73 char *ptr = perf->buf; in refill_buf()
74 int rem = sizeof(perf->buf); in refill_buf()
77 if ((perf->cnt++ % 32) == 0) { in refill_buf()
97 ret = wait_sample(perf); in refill_buf()
[all …]
Dmsm_drv.h112 struct msm_perf_state *perf; member
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/bios/
Dperf.c33 u16 perf = 0x0000; in nvbios_perf_table() local
37 perf = nvbios_rd16(bios, bit_P.offset + 0); in nvbios_perf_table()
38 if (perf) { in nvbios_perf_table()
39 *ver = nvbios_rd08(bios, perf + 0); in nvbios_perf_table()
40 *hdr = nvbios_rd08(bios, perf + 1); in nvbios_perf_table()
42 *cnt = nvbios_rd08(bios, perf + 5); in nvbios_perf_table()
43 *len = nvbios_rd08(bios, perf + 2); in nvbios_perf_table()
44 *snr = nvbios_rd08(bios, perf + 4); in nvbios_perf_table()
45 *ssz = nvbios_rd08(bios, perf + 3); in nvbios_perf_table()
46 return perf; in nvbios_perf_table()
[all …]
DKbuild18 nvkm-y += nvkm/subdev/bios/perf.o
/linux-4.4.14/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-evlist mainporcelain common
13 perf-inject mainporcelain common
[all …]
DBuild1 perf-y += builtin-bench.o
2 perf-y += builtin-annotate.o
3 perf-y += builtin-diff.o
4 perf-y += builtin-evlist.o
5 perf-y += builtin-help.o
6 perf-y += builtin-sched.o
7 perf-y += builtin-buildid-list.o
8 perf-y += builtin-buildid-cache.o
9 perf-y += builtin-list.o
10 perf-y += builtin-record.o
[all …]
D.gitignore5 perf
6 perf-read-vdso32
7 perf-read-vdsox32
8 perf-help
9 perf-record
10 perf-report
11 perf-stat
12 perf-top
13 perf*.1
14 perf*.xml
[all …]
DMakefile.perf178 SCRIPT_SH += perf-archive.sh
179 SCRIPT_SH += perf-with-kcore.sh
215 python-clean := $(call QUIET_CLEAN, python) $(RM) -r $(PYTHON_EXTBUILD) $(OUTPUT)python/perf.so
220 $(OUTPUT)python/perf.so: $(PYTHON_EXT_SRCS) $(PYTHON_EXT_DEPS) $(LIBTRACEEVENT_DYNAMIC_LIST)
225 cp $(PYTHON_EXTBUILD_LIB)perf.so $(OUTPUT)python/
232 PROGRAMS += $(OUTPUT)perf
235 PROGRAMS += $(OUTPUT)perf-read-vdso32
239 PROGRAMS += $(OUTPUT)perf-read-vdsox32
246 OTHER_PROGRAMS = $(OUTPUT)perf
304 strip: $(PROGRAMS) $(OUTPUT)perf
[all …]
Dperf-archive.sh5 PERF_DATA=perf.data
21 BUILDIDS=$(mktemp /tmp/perf-archive-buildids.XXXXXX)
24 perf buildid-list -i $PERF_DATA --with-hits | grep -v "^$NOBUILDID " > $BUILDIDS
31 MANIFEST=$(mktemp /tmp/perf-archive-manifest.XXXXXX)
Dperf-with-kcore.sh29 PERF=`which perf || true`
52 rm -f perf.data.junk
53 ("$PERF" record -o perf.data.junk "${PERF_OPTIONS[@]}" -- sleep 60) >/dev/null 2>/dev/null &
67 rm perf.data.junk
76 rm perf.data.junk
Dperf-completion.sh241 compdef _perf perf
245 type perf &>/dev/null &&
257 complete -o bashdefault -o default -o nospace -F _perf perf 2>/dev/null \
258 || complete -o default -o nospace -F _perf perf
DCREDITS1 Most of the infrastructure that 'perf' uses here has been reused
DMANIFEST1 tools/perf
Ddesign.txt462 should select PERF_USE_VMALLOC in order to avoid these for perf mmap().
/linux-4.4.14/tools/perf/tests/
DBuild1 perf-y += builtin-test.o
2 perf-y += parse-events.o
3 perf-y += dso-data.o
4 perf-y += attr.o
5 perf-y += vmlinux-kallsyms.o
6 perf-y += openat-syscall.o
7 perf-y += openat-syscall-all-cpus.o
8 perf-y += openat-syscall-tp-fields.o
9 perf-y += mmap-basic.o
10 perf-y += perf-record.o
[all …]
Dmake6 @echo "Testing Makefile.perf"; $(MAKE) -sf tests/make MK=Makefile.perf
29 make_python_perf_so := python/perf.so
52 make_perf_o := perf.o
75 # Makefile because we detect clean target in Makefile.perf and
145 test_make_python_perf_so := test -f $(PERF)/python/perf.so
147 test_make_perf_o := test -f $(PERF)/perf.o
159 installed_files_bin := bin/perf
160 installed_files_bin += etc/bash_completion.d/perf
161 installed_files_bin += libexec/perf-core/perf-archive
192 test_make_install_man := test -f $$TMP_DEST/share/man/man1/perf.1
[all …]
Dperf-targz-src-pkg12 make perf-targz-src-pkg > /dev/null
13 TARBALL=$(ls -rt perf-*.tar.gz)
18 make -C $TMP_DEST/perf*/tools/perf > /dev/null 2>&1
Dattr.c141 static int run_dir(const char *d, const char *perf) in run_dir() argument
151 d, d, perf, vcnt, v); in run_dir()
Dattr.py128 self.perf = options.perf
172 self.perf, self.command, tempdir, self.args)
/linux-4.4.14/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 …]
/linux-4.4.14/tools/perf/Documentation/
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 …]
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-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]
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 …]
Dandroid.txt1 How to compile perf for Android
22 perf uses some bionic enhancements that are not included in these NDK versions.
48 II. Compile perf for Android
56 III. Install perf
59 Install perf using:
60 adb push perf /data/perf
62 If you also want to use perf-archive you need busybox tools for Android.
63 For installing perf-archive, you first need to replace #!/bin/bash with #!/system/bin/sh:
64 sed 's/#!\/bin\/bash/#!\/system\/bin\/sh/g' perf-archive >> /tmp/perf-archive
65 chmod +x /tmp/perf-archive
[all …]
Dperf-sched.txt1 perf-sched(1)
6 perf-sched - Tool to trace/measure scheduler properties (latencies)
11 'perf sched' {record|latency|map|replay|script}
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 script' to see a detailed trace of the workload that
24 was recorded (aliased to 'perf script' for now).
26 'perf sched replay' to simulate the workload that was recorded
27 via perf sched record. (this is done by starting up mockup threads
[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)
37 linkperf:perf-record[1], linkperf:perf-list[1],
38 linkperf:perf-report[1]
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]
Dperf-help.txt1 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
Dintel-bts.txt18 'perf record'.
21 perf record
27 The Intel BTS kernel driver creates a new PMU for Intel BTS. The perf record
48 perf script
51 By default, perf script will decode trace data found in the perf.data file.
63 perf script has an option (-D) to "dump" the events i.e. display the binary
72 perf report
75 By default, perf report will decode trace data found in the perf.data file.
77 perf script.
80 perf inject
[all …]
Dperf-script.txt1 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 …]
Dperf.txt1 perf(1)
6 perf - Performance analysis tools for Linux
11 'perf' [--version] [--help] [OPTIONS] COMMAND [ARGS]
32 Display perf version.
36 Run perf help command.
47 linkperf:perf-stat[1], linkperf:perf-top[1],
48 linkperf:perf-record[1], linkperf:perf-report[1],
49 linkperf:perf-list[1]
Dperf-diff.txt1 perf-diff(1)
6 perf-diff - Read perf.data files and display the differential profile
11 'perf diff' [baseline file] [data file1] [[data file2] ... ]
15 This command displays the performance difference amongst two or more perf.data
16 files captured via perf record.
18 If no parameters are passed it will assume perf.data.old and perf.data.
21 specified perf.data files.
24 As the perf.data files could come from different binaries, the symbols addresses
25 could vary. So perf diff is based on the comparison of the files and
62 Please see description of --sort in the perf-report man page.
[all …]
Dperf-timechart.txt1 perf-timechart(1)
6 perf-timechart - Tool to visualize total system behavior during a workload
11 'perf timechart' [<timechart options>] {record} [<record options>]
15 There are two variants of perf timechart:
17 'perf timechart record <command>' to record the system level events
22 'perf timechart' to turn a trace into a Scalable Vector Graphics file,
24 on the events in the perf.data file, timechart will contain scheduler/cpu
40 Select the input file (default: perf.data unless stdin is a fifo)
99 $ perf timechart record git pull
101 [ perf record: Woken up 13 times to write data ]
[all …]
Dperf-mem.txt1 perf-mem(1)
6 perf-mem - Profile memory accesses
11 'perf mem' [<options>] (record [<command>] | report)
15 "perf mem record" runs a command and gathers memory operation data
16 from it, into perf.data. Perf record options are accepted and are passed through.
18 "perf mem report" displays the result. It invokes perf report with the
48 option can be passed in record mode. It will be interpreted the same way as perf
53 linkperf:perf-record[1], linkperf:perf-report[1]
Dperf-inject.txt1 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
58 linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1]
Dperf-script-python.txt1 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 …]
Dperf-data.txt1 perf-data(1)
6 perf-data - Data file related processing
11 'perf data' [<common options>] <command> [<options>]",
20 Converts perf data file into another format (only CTF [1] format is support by now).
23 perf --debug data-convert data convert ...
31 Specify input perf data file path.
39 linkperf:perf[1]
Dperf-kmem.txt1 perf-kmem(1)
6 perf-kmem - Tool to trace/measure kernel memory 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 unless stdin is a fifo)
60 Show live page stat. The perf kmem shows total allocation stat by
66 linkperf:perf-record[1]
Dexamples.txt3 ****** 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 -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 …]
Dperf-trace.txt1 perf-trace(1)
6 perf-trace - strace inspired tool
11 'perf trace'
12 'perf trace record'
20 This is a live mode tool in addition to working with perf.data files like
21 the other perf tools. Files can be generated using the 'perf record' command
23 Alternatively, 'perf trace record' can be used as a shortcut to
26 The following options apply to perf trace; options to perf trace record are
27 found in the perf record man page.
89 Process events from a given perf data file.
[all …]
Dperf-probe.txt1 perf-probe(1)
6 perf-probe - Define new dynamic tracepoints
11 'perf probe' [options] --add='PROBE' [...]
13 'perf probe' [options] PROBE
15 'perf probe' [options] --del='[GROUP:]EVENT' [...]
17 'perf probe' --list[=[GROUP:]EVENT]
19 'perf probe' [options] --line='LINE'
21 'perf probe' [options] --vars='PROBEPOINT'
23 'perf probe' [options] --funcs
40 Specify module name in which perf-probe searches probe points
[all …]
Dperf-bench.txt1 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 a general framework for benchmark suites.
31 % perf bench sched pipe # with no style specified
42 % perf bench --format=simple sched pipe # specified simple
92 % perf bench sched messaging # run with default
98 % perf bench sched messaging -t -g 20 # be multi-thread, with 20 groups
119 % perf bench sched pipe
126 % perf bench sched pipe -l 1000 # loop 1000
[all …]
Dasciidoc.conf30 ifndef::perf-asciidoc-no-roff[]
45 endif::perf-asciidoc-no-roff[]
47 ifdef::perf-asciidoc-no-roff[]
66 endif::perf-asciidoc-no-roff[]
77 <refmiscinfo class="source">perf</refmiscinfo>
79 <refmiscinfo class="manual">perf Manual</refmiscinfo>
Dperf-test.txt1 perf-test(1)
6 perf-test - Runs sanity tests.
11 'perf test [<options>] [{list <test-name-fragment>|[<test-name-fragments>|<test-numbers>]}]'
18 To get a list of available tests use 'perf test list', specifying a test name
22 from 'perf test list'.
Dintel-pt.txt16 Trace data is collected by 'perf record' and stored within the perf.data file.
17 See below for options to 'perf record'.
25 samples output by perf hardware events, for example as though the "instructions"
27 'perf script', 'perf report' and 'perf inject'. See below for more information
52 Data is captured with 'perf record' e.g. to trace 'ls' userspace-only:
54 perf record -e intel_pt//u ls
56 And profiled with 'perf report' e.g.
58 perf report
63 as the data capture. A script perf-with-kcore can do that, but beware that the
64 script makes use of 'sudo' to copy /proc/kcore. If you have perf installed
[all …]
Dperf-list.txt1 perf-list(1)
6 perf-list - List all symbolic event types
11 'perf list' [hw|sw|cache|tracepoint|pmu|event_glob]
16 various perf commands with the -e option.
56 perf record -a -e cpu-cycles:p ... # use ibs op counting cycles
57 perf record -a -e r076:p ... # same as -e cpu-cycles:p
58 perf record -a -e r0C1:p ... # use ibs op counting micro-ops
62 Even when an event is not available in a symbolic form within perf right now,
88 perf stat -e r1a8 -a sleep 1
89 perf record -e r1a8 ...
[all …]
Dperf-script-perl.txt1 perf-script-perl(1)
6 perf-script-perl - Process trace data with a Perl script
11 'perf script' [-s [Perl]:script[.pl] ]
16 This perf script option is used to process perf script data using perf's
24 You can avoid reading the rest of this document by running 'perf script
25 -g perl' in the same directory as an existing perf.data trace file.
31 ~/libexec/perf-core/scripts/perl for typical examples showing how to
33 the check-perf-script.pl script, while not interesting for its results,
39 When perf script is invoked using a trace script, a user-defined
47 available as calls back into the perf executable (see below).
[all …]
Dperf-buildid-cache.txt1 perf-buildid-cache(1)
6 perf-buildid-cache - Manage build-id cache.
11 'perf buildid-cache <options>'
28 running 'perf buildid-cache' as root may update root's build-id cache
52 (or remote) perf.data. Only if there is already a cache which has
63 linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-buildid-list[1]
Dperf-annotate.txt1 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 unless stdin is a fifo)
101 linkperf:perf-record[1], linkperf:perf-report[1]
DMakefile6 $(wildcard perf-*.txt)) \
7 perf.txt
42 htmldir?=$(prefix)/share/doc/perf-doc
43 pdfdir?=$(prefix)/share/doc/perf-doc
108 ASCIIDOC_EXTRA += -a perf-asciidoc-no-roff
114 ASCIIDOC_EXTRA += -a perf-asciidoc-no-roff
175 info: $(OUTPUT)perf.info $(OUTPUT)perfman.info
208 $(INSTALL) -m 644 $(OUTPUT)perf.info $(OUTPUT)perfman.info $(DESTDIR)$(infodir); \
210 $(INSTALL_INFO) --info-dir=$(DESTDIR)$(infodir) perf.info ;\
258 $(OUTPUT)perf.info $(OUTPUT)perfman.info \
[all …]
Dperf-report.txt1 perf-report(1)
6 perf-report - Read perf.data (created by perf record) and display the profile
11 'perf report' [-i <file> | --input=file]
16 via perf record.
22 Input file name. (default: perf.data unless stdin is a fifo)
283 Display extended information about the perf.data file. This adds
291 perf.data file must have been obtained using perf record -b or
292 perf record --branch-filter xxx where xxx is a branch filter option.
293 perf report is able to auto-detect whether a perf.data file contains
317 to build the histograms. To generate meaningful output, the perf.data
[all …]
Dperf-stat.txt1 perf-stat(1)
6 perf-stat - Run a command and gather performance counter statistics
11 'perf stat' [-e <EVENT> | --event=EVENT] [-a] <command>
12 'perf stat' [-e <EVENT> | --event=EVENT] [-a] -- <command> [<options>]
30 - a symbolic event name (use 'perf list' to list all events)
128 3>results perf stat --log-fd 3 -- $cmd
129 3>>results perf stat --log-fd 3 --append -- $cmd
135 perf stat --repeat 10 --null --sync --pre 'make -s O=defconfig-build/clean' -- make -s -j64 O=defco…
141 example: 'perf stat -I 1000 -e cycles -a sleep 5'
173 $ perf stat -- make -j
[all …]
Dperf-record.txt1 perf-record(1)
6 perf-record - Run a command and record its profile into perf.data
11 'perf record' [-e <EVENT> | --event=EVENT] [-l] [-a] <command>
12 'perf record' [-e <EVENT> | --event=EVENT] [-l] [-a] -- <command> [<options>]
17 from it, into perf.data - without displaying anything.
19 This file can then be inspected later on, using 'perf report'.
31 - a symbolic event name (use 'perf list' to list all events)
76 "perf report" to view group events together.
83 --exclude-perf::
84 Don't record events issued by perf itself. This option should follow
[all …]
Dperf-top.txt1 perf-top(1)
6 perf-top - System profiling tool.
11 'perf top' [-e <EVENT> | --event=EVENT] [<options>]
41 (use 'perf list' to list all events) or a raw PMU
120 Please see description of --sort in the perf-report man page.
165 implies -g. See `--call-graph` section in perf-record and
166 perf-report man pages for details.
223 For a full list of modifiers please see the perf record manpage.
269 linkperf:perf-stat[1], linkperf:perf-list[1], linkperf:perf-report[1]
Djit-interface.txt1 perf supports a simple JIT interface to resolve symbols for dynamic code generated
4 The JIT has to write a /tmp/perf-%d.map (%d = pid of process) file
Dcallchain-overhead-calculation.txt4 perf collects callchains. The 'self' overhead is simply calculated by
6 This is the value that perf shows traditionally and sum of all the
45 in the usual (self-overhead-only) output of perf report:
107 'report.children = false' or 'top.children = false' in the perf config
/linux-4.4.14/tools/perf/bench/
DBuild1 perf-y += sched-messaging.o
2 perf-y += sched-pipe.o
3 perf-y += mem-functions.o
4 perf-y += futex-hash.o
5 perf-y += futex-wake.o
6 perf-y += futex-wake-parallel.o
7 perf-y += futex-requeue.o
8 perf-y += futex-lock-pi.o
10 perf-$(CONFIG_X86_64) += mem-memcpy-x86-64-asm.o
11 perf-$(CONFIG_X86_64) += mem-memset-x86-64-asm.o
[all …]
/linux-4.4.14/drivers/cpufreq/
Dacpi-cpufreq.c208 struct acpi_processor_performance *perf; in extract_io() local
211 perf = to_perf_data(data); in extract_io()
213 for (i = 0; i < perf->state_count; i++) { in extract_io()
214 if (value == perf->states[i].status) in extract_io()
223 struct acpi_processor_performance *perf; in extract_msr() local
230 perf = to_perf_data(data); in extract_msr()
233 if (msr == perf->states[pos->driver_data].status) in extract_msr()
339 struct acpi_processor_performance *perf; in get_cur_val() local
356 perf = to_perf_data(data); in get_cur_val()
357 cmd.addr.io.port = perf->control_register.address; in get_cur_val()
[all …]
/linux-4.4.14/tools/perf/python/
Dtwatch.py16 import perf
19 cpus = perf.cpu_map()
20 threads = perf.thread_map(thread)
21 evsel = perf.evsel(type = perf.TYPE_SOFTWARE,
22 config = perf.COUNT_SW_DUMMY,
26 sample_type = perf.SAMPLE_PERIOD | perf.SAMPLE_TID | perf.SAMPLE_CPU)
36 evlist = perf.evlist(cpus, threads)
/linux-4.4.14/scripts/package/
DMakefile115 perf-tar=perf-$(KERNELVERSION)
119 git --git-dir=$(srctree)/.git archive --prefix=$(perf-tar)/ \
121 echo $$(cat $(srctree)/tools/perf/MANIFEST)) \
122 -o $(perf-tar).tar; \
123 mkdir -p $(perf-tar); \
124 git --git-dir=$(srctree)/.git rev-parse HEAD > $(perf-tar)/HEAD; \
125 (cd $(srctree)/tools/perf; \
126 util/PERF-VERSION-GEN ../../$(perf-tar)/ 2>/dev/null); \
127 tar rf $(perf-tar).tar $(perf-tar)/HEAD $(perf-tar)/PERF-VERSION-FILE; \
128 rm -r $(perf-tar); \
[all …]
/linux-4.4.14/lib/raid6/
Dalgos.c134 unsigned long perf, bestgenperf, bestxorperf, j0, j1; in raid6_choose_gen() local
144 perf = 0; in raid6_choose_gen()
153 perf++; in raid6_choose_gen()
157 if (perf > bestgenperf) { in raid6_choose_gen()
158 bestgenperf = perf; in raid6_choose_gen()
162 (perf*HZ) >> (20-16+RAID6_TIME_JIFFIES_LG2)); in raid6_choose_gen()
167 perf = 0; in raid6_choose_gen()
177 perf++; in raid6_choose_gen()
182 bestxorperf = perf; in raid6_choose_gen()
185 (perf*HZ) >> (20-16+RAID6_TIME_JIFFIES_LG2+1)); in raid6_choose_gen()
/linux-4.4.14/tools/perf/scripts/perl/Perf-Trace-Util/
DREADME4 This module contains utility functions for use with perf script.
7 that the core perf support for Perl calls on and should always be
10 interface that allows scripts to access data in the embedding perf
13 The Perl->C perf interface is completely driven by Context.xs. If you
15 perf executable, you add desciptions of the new functions here.
16 scripting_context is a pointer to the perf data in the perf executable
32 You should then be able to run the normal perf make as usual.
36 Building perf with perf script Perl scripting should install this
/linux-4.4.14/Documentation/arm/
DCCN.txt9 PMU (perf) driver
12 The CCN driver registers a perf PMU driver, which provides
19 events, that can be used with perf tool. For example "xp_valid_flit"
43 Example of perf tool use:
45 / # perf list | grep ccn
51 / # perf stat -a -e ccn/cycles/,ccn/xp_valid_flit,xp=1,port=0,vc=1,dir=1/ \
54 The driver does not support sampling, therefore "perf record" will
55 not work. Per-task (without "-a") perf sessions are not supported.
D00-INDEX6 - Cache Coherent Network ring-bus and perf PMU driver.
/linux-4.4.14/Documentation/trace/
Dtracepoint-analysis.txt21 assumed that the PCL tool tools/perf has been installed and is in your path.
40 are available with the perf tool. Getting a list of available events is a
43 $ perf list 2>&1 | grep Tracepoint
95 $ perf stat -a \
122 $ perf stat -e kmem:mm_page_alloc -e kmem:mm_page_free \
147 occurrences are useful to the performance analyst, then perf can be used.
149 $ perf stat --repeat 5 -e kmem:mm_page_alloc -e kmem:mm_page_free
171 $ perf stat -e kmem:mm_page_alloc -e kmem:mm_page_free \
222 $ perf record -c 1 \
227 [ perf record: Captured and wrote 0.733 MB perf.data (~32010 samples) ]
[all …]
Dkprobetrace.txt105 the ABI, please try to use probe subcommand of perf-tools (you can find it
106 under tools/perf/).
Dftrace.txt348 perf: This makes ftrace use the same clock that perf uses.
349 Eventually perf will be able to read ftrace buffers
2406 also for any other uses (perf, kprobes, stack tracing, profiling, etc).
/linux-4.4.14/arch/sh/kernel/cpu/sh4/
DMakefile13 perf-$(CONFIG_CPU_SUBTYPE_SH7750) := perf_event.o
14 perf-$(CONFIG_CPU_SUBTYPE_SH7750S) := perf_event.o
15 perf-$(CONFIG_CPU_SUBTYPE_SH7091) := perf_event.o
36 obj-$(CONFIG_PERF_EVENTS) += $(perf-y)
/linux-4.4.14/tools/perf/config/
DMakefile2 ifeq ($(src-perf),)
3 src-perf := $(srctree)/tools/perf
6 ifeq ($(obj-perf),)
7 obj-perf := $(OUTPUT)
10 ifneq ($(obj-perf),)
11 obj-perf := $(abspath $(obj-perf))/
20 include $(src-perf)/config/Makefile.arch
111 -include $(src-perf)/arch/$(ARCH)/Makefile
117 include $(src-perf)/config/utilities.mak
198 CFLAGS += -I$(src-perf)/util/include
[all …]
/linux-4.4.14/drivers/xen/
Dxen-acpi-processor.c222 dst_perf = &op.u.set_pminfo.perf; in push_pxx_to_hypervisor()
250 struct acpi_processor_performance *perf; in push_pxx_to_hypervisor() local
253 perf = _pr->performance; in push_pxx_to_hypervisor()
255 for (i = 0; i < perf->state_count; i++) { in push_pxx_to_hypervisor()
257 (i == perf->state ? '*' : ' '), i, in push_pxx_to_hypervisor()
258 (u32) perf->states[i].core_frequency, in push_pxx_to_hypervisor()
259 (u32) perf->states[i].power, in push_pxx_to_hypervisor()
260 (u32) perf->states[i].transition_latency); in push_pxx_to_hypervisor()
542 struct acpi_processor_performance *perf; in xen_acpi_processor_init() local
545 perf = per_cpu_ptr(acpi_perf_data, i); in xen_acpi_processor_init()
[all …]
/linux-4.4.14/arch/arm/mach-vexpress/
Dspc.c260 u32 perf; in ve_spc_get_performance() local
264 perf = readl_relaxed(info->baseaddr + perf_cfg_reg); in ve_spc_get_performance()
265 if (perf >= info->num_opps[cluster]) in ve_spc_get_performance()
268 opps += perf; in ve_spc_get_performance()
323 int ret, perf, req_type; in ve_spc_set_performance() local
335 perf = ve_spc_find_performance_index(cluster, freq); in ve_spc_set_performance()
337 if (perf < 0) in ve_spc_set_performance()
338 return perf; in ve_spc_set_performance()
346 writel(perf, info->baseaddr + perf_cfg_reg); in ve_spc_set_performance()
/linux-4.4.14/tools/perf/scripts/perl/bin/
Dfailed-syscalls-record2 (perf record -e raw_syscalls:sys_exit $@ || \
3 perf record -e syscalls:sys_exit $@) 2> /dev/null
Dwakeup-latency-record2 perf record -e sched:sched_switch -e sched:sched_wakeup $@
Drw-by-file-record2 perf record -e syscalls:sys_enter_read -e syscalls:sys_enter_write $@
Dwakeup-latency-report3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/perl/wakeup-latency.pl
Dcheck-perf-trace-record2 perf record -a -e kmem:kmalloc -e irq:softirq_entry -e kmem:kfree
Drw-by-pid-report3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/perl/rw-by-pid.pl
Drw-by-pid-record2 perf record -e syscalls:sys_enter_read -e syscalls:sys_exit_read -e syscalls:sys_enter_write -e sys…
Drwtop-record2 perf record -e syscalls:sys_enter_read -e syscalls:sys_exit_read -e syscalls:sys_enter_write -e sys…
Drw-by-file-report10 perf script $@ -s "$PERF_EXEC_PATH"/scripts/perl/rw-by-file.pl $comm
Dfailed-syscalls-report10 perf script $@ -s "$PERF_EXEC_PATH"/scripts/perl/failed-syscalls.pl $comm
Drwtop-report20 perf script $@ -s "$PERF_EXEC_PATH"/scripts/perl/rwtop.pl $interval
/linux-4.4.14/tools/perf/scripts/python/bin/
Dfailed-syscalls-by-pid-record2 (perf record -e raw_syscalls:sys_exit $@ || \
3 perf record -e syscalls:sys_exit $@) 2> /dev/null
Dsctop-record2 (perf record -e raw_syscalls:sys_enter $@ || \
3 perf record -e syscalls:sys_enter $@) 2> /dev/null
Dsyscall-counts-by-pid-record2 (perf record -e raw_syscalls:sys_enter $@ || \
3 perf record -e syscalls:sys_enter $@) 2> /dev/null
Dsyscall-counts-record2 (perf record -e raw_syscalls:sys_enter $@ || \
3 perf record -e syscalls:sys_enter $@) 2> /dev/null
Dexport-to-postgresql-record8 perf record $@
Devent_analyzing_sample-record8 perf record $@
Dnet_dropmonitor-record2 perf record -e skb:kfree_skb $@
Dfutex-contention-record2 perf record -e syscalls:sys_enter_futex -e syscalls:sys_exit_futex $@
Dnet_dropmonitor-report4 perf script -s "$PERF_EXEC_PATH"/scripts/python/net_dropmonitor.py $@
Devent_analyzing_sample-report3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/event_analyzing_sample.py
Dcompaction-times-report4 perf script -s "$PERF_EXEC_PATH"/scripts/python/compaction-times.py $@
Dnetdev-times-report5 perf script -s "$PERF_EXEC_PATH"/scripts/python/netdev-times.py $@
Dsched-migration-report3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
Dfutex-contention-report4 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/futex-contention.py
Dsched-migration-record2 perf record -m 16384 -e sched:sched_wakeup -e sched:sched_wakeup_new -e sched:sched_switch -e sched…
Dcompaction-times-record2 perf record -e compaction:mm_compaction_begin -e compaction:mm_compaction_end -e compaction:mm_comp…
Dsyscall-counts-report10 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/syscall-counts.py $comm
Dsyscall-counts-by-pid-report10 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/syscall-counts-by-pid.py $comm
Dfailed-syscalls-by-pid-report10 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/failed-syscalls-by-pid.py $comm
Dsctop-report24 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sctop.py $comm $interval
Dnetdev-times-record2 perf record -e net:net_dev_xmit -e net:net_dev_queue \
Dexport-to-postgresql-report29 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/export-to-postgresql.py $dbname $columns $calls
/linux-4.4.14/tools/
DMakefile66 PERF_O = $(if $(O),$(O)/tools/perf,)
68 perf: FORCE target
70 $(Q)$(MAKE) --no-print-directory -C perf O=$(PERF_O) subdir=
85 perf selftests turbostat usb \
/linux-4.4.14/Documentation/features/perf/perf-regs/
Darch-support.txt2 # Feature name: perf-regs
4 # description: arch supports perf events register access
/linux-4.4.14/Documentation/features/perf/perf-stackdump/
Darch-support.txt2 # Feature name: perf-stackdump
4 # description: arch supports perf events stack dumps
/linux-4.4.14/tools/perf/util/
Dsetup.py37 perf = Extension('perf', variable
51 ext_modules=[perf],
Dpython-ext-sources2 # List of files needed by perf python extension
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-event_source-devices-hv_gpci15 in arch/powerpc/perf/hv-gpci.h).
22 in arch/powerpc/perf/hv-gpci.h).
29 in arch/powerpc/perf/hv-gpci.h).
Dsysfs-bus-event_source-devices-events19 using the 'perf(1)' tool.
26 "raw code" for the perf event identified by the file's
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Dgf119.fuc441 #include "perf.fuc"
52 #include "perf.fuc"
65 #include "perf.fuc"
Dgk208.fuc541 #include "perf.fuc"
52 #include "perf.fuc"
65 #include "perf.fuc"
Dgt215.fuc341 #include "perf.fuc"
52 #include "perf.fuc"
65 #include "perf.fuc"
Dgf100.fuc341 #include "perf.fuc"
52 #include "perf.fuc"
65 #include "perf.fuc"
Dperf.fuc42 // $r15 - current (perf)
53 // $r15 - current (perf)
/linux-4.4.14/drivers/clk/
Dclk-u300.c569 u16 perf = syscon_get_perf(); in syscon_clk_recalc_rate() local
578 switch(perf) { in syscon_clk_recalc_rate()
589 switch(perf) { in syscon_clk_recalc_rate()
601 switch(perf) { in syscon_clk_recalc_rate()
612 switch(perf) { in syscon_clk_recalc_rate()
982 u16 perf = syscon_get_perf(); in mclk_clk_recalc_rate() local
984 switch (perf) { in mclk_clk_recalc_rate()
/linux-4.4.14/Documentation/
Ddontdiff193 perf.data
194 perf.data.old
195 perf-archive
Dlockup-watchdogs.txt36 perf subsystems, respectively. A direct consequence of this is that,
41 task. An NMI perf event is generated every "watchdog_thresh"
45 'hardlockup detector' (the handler for the NMI perf event) will
62 administrators to configure the period of the hrtimer and the perf
Dstatic-keys.txt251 'pipe-test' (also known as 'perf bench sched pipe') can be used to show the
/linux-4.4.14/scripts/kconfig/
Dzconf.l2 %option 8bit nodefault perf-report perf-report
/linux-4.4.14/tools/perf/arch/x86/tests/
DBuild6 libperf-y += perf-time-to-tsc.o
/linux-4.4.14/Documentation/features/perf/kprobes-event/
Darch-support.txt4 # description: arch supports kprobes with perf events
/linux-4.4.14/Documentation/powerpc/
Dpmu-ebb.txt45 concurrently with regular 'perf' commands, or any other perf events.
47 It is however safe to run 'perf' commands on a process which is using EBBs. The
48 kernel will in general schedule the EBB event, and perf will be notified that
/linux-4.4.14/arch/metag/kernel/
DMakefile28 obj-$(CONFIG_PERF_EVENTS) += perf/
/linux-4.4.14/arch/arm/kvm/
DMakefile22 obj-y += coproc.o coproc_a15.o coproc_a7.o mmio.o psci.o perf.o
/linux-4.4.14/tools/lib/api/
DMakefile2 include ../../perf/config/utilities.mak # QUIET_CLEAN
/linux-4.4.14/arch/arm64/kvm/
DMakefile16 kvm-$(CONFIG_KVM_ARM_HOST) += $(ARM)/psci.o $(ARM)/perf.o
/linux-4.4.14/arch/parisc/kernel/
DMakefile35 obj-$(CONFIG_64BIT) += perf.o perf_asm.o $(obj64-y)
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/therm/
Dpriv.h41 struct nvbios_perf_fan perf; member
Dfanpwm.c66 divs = fan->base.perf.pwm_divisor; in nvkm_fanpwm_set()
Dfan.c271 nvbios_perf_fan_parse(bios, &therm->fan->perf); in nvkm_therm_fan_ctor()
/linux-4.4.14/Documentation/x86/
Dtlb.txt57 performance counters and 'perf stat', like this:
59 perf stat -e
/linux-4.4.14/drivers/staging/android/
DTODO17 dma api's back (this is absolutely needed for high-perf gpu drivers): Add an
/linux-4.4.14/tools/build/Documentation/
DBuild.txt4 The perf build framework was adopted from the kernel build system, hence the
138 CFLAGS_perf.o += '...' - alters CFLAGS for perf.o object
/linux-4.4.14/tools/perf/util/intel-pt-decoder/
DBuild11 @(test -d ../../kernel -a -d ../../tools -a -d ../perf && (( \
/linux-4.4.14/arch/
DKconfig101 enable instrumentation applications (such as 'perf probe')
274 System hardware can generate an NMI using the perf event
281 Support selective register dumps for perf events. This includes
287 Support user stack dumps for perf event samples. This needs
/linux-4.4.14/drivers/
DMakefile166 obj-$(CONFIG_PERF_EVENTS) += perf/
DKconfig183 source "drivers/perf/Kconfig"
/linux-4.4.14/tools/power/cpupower/po/
Dde.po683 " -b, --perf-bias [VAL] Sets CPU's power vs performance policy on some\n"
702 msgid "--perf-bias param out of range [0-%d]\n"
727 msgid "Error setting perf-bias value on CPU %d\n"
738 " -b, --perf-bias Gets CPU's power vs performance policy on some\n"
788 msgid "Could not read perf-bias value\n"
793 msgid "perf-bias: %d\n"
Dit.po680 " -b, --perf-bias [VAL] Sets CPU's power vs performance policy on some\n"
699 msgid "--perf-bias param out of range [0-%d]\n"
724 msgid "Error setting perf-bias value on CPU %d\n"
735 " -b, --perf-bias Gets CPU's power vs performance policy on some\n"
786 msgid "Could not read perf-bias value\n"
791 msgid "perf-bias: %d\n"
Dcs.po672 " -b, --perf-bias [VAL] Sets CPU's power vs performance policy on some\n"
691 msgid "--perf-bias param out of range [0-%d]\n"
716 msgid "Error setting perf-bias value on CPU %d\n"
727 " -b, --perf-bias Gets CPU's power vs performance policy on some\n"
777 msgid "Could not read perf-bias value\n"
782 msgid "perf-bias: %d\n"
Dfr.po672 " -b, --perf-bias [VAL] Sets CPU's power vs performance policy on some\n"
691 msgid "--perf-bias param out of range [0-%d]\n"
716 msgid "Error setting perf-bias value on CPU %d\n"
727 " -b, --perf-bias Gets CPU's power vs performance policy on some\n"
777 msgid "Could not read perf-bias value\n"
782 msgid "perf-bias: %d\n"
Dpt.po682 " -b, --perf-bias [VAL] Sets CPU's power vs performance policy on some\n"
701 msgid "--perf-bias param out of range [0-%d]\n"
726 msgid "Error setting perf-bias value on CPU %d\n"
737 " -b, --perf-bias Gets CPU's power vs performance policy on some\n"
788 msgid "Could not read perf-bias value\n"
793 msgid "perf-bias: %d\n"
/linux-4.4.14/kernel/trace/
DKconfig415 This option is also required by perf-probe subcommand of perf tools.
416 If you want to use perf tools, this option is strongly recommended.
432 This option is required if you plan to use perf-probe subcommand
433 of perf tools on user space applications.
/linux-4.4.14/drivers/media/platform/sti/bdisp/
Dbdisp-debug.c650 bdisp_dbg_declare(perf);
673 if (!bdisp_dbg_create_entry(perf)) in bdisp_debugfs_create()
/linux-4.4.14/arch/arc/kernel/
Dentry-arcv2.S49 VECTOR handle_interrupt ; (20) perf Interrupt
/linux-4.4.14/drivers/bus/
DKconfig55 PMU (perf) driver supporting the ARM CCN (Cache Coherent Network)
/linux-4.4.14/include/xen/interface/
Dplatform.h421 struct xen_processor_performance perf; /* Px: _PPC/_PCT/_PSS/_PSD */ member
/linux-4.4.14/arch/powerpc/platforms/pseries/
DKconfig124 Enable access to hypervisor supplied counters in perf. Currently,
/linux-4.4.14/arch/sh/
DKconfig738 bool "Enable hardware performance counter support for perf events"
742 Enable hardware performance counter support for perf events. If
743 disabled, perf events will use software events only.
/linux-4.4.14/Documentation/sysctl/
Dkernel.txt604 use to handle perf sampling events. If the perf subsystem
609 Some perf sampling happens in NMIs. If these samples
614 0: disable the mechanism. Do not monitor or correct perf's
617 1-100: attempt to throttle perf's sample rate to this
/linux-4.4.14/arch/powerpc/
DMakefile236 core-$(CONFIG_PERF_EVENTS) += arch/powerpc/perf/
/linux-4.4.14/Documentation/timers/
DNO_HZ.txt165 4. If there are more perf events pending than the hardware can
169 preventing CPUs with large numbers of perf events pending from
/linux-4.4.14/init/
DKconfig1629 See tools/perf/design.txt for details.
1634 See tools/perf/design.txt for details
1662 system call and used by the "perf" utility in tools/perf/. It
1670 bool "Debug: use vmalloc to back perf mmap() buffers"
1674 Use vmalloc memory to back perf mmap() buffers.
/linux-4.4.14/lib/
DKconfig.debug1041 This also enables lock events required by "perf lock",
1042 subcommand of perf.
1043 If you want to use "perf lock", you also need to turn on
/linux-4.4.14/arch/mips/
DKconfig2473 bool "Enable hardware performance counter support for perf events"
2477 Enable hardware performance counter support for perf events. If
2478 disabled, perf events will use software events only.
/linux-4.4.14/
DMAINTAINERS838 F: drivers/perf/arm_pmu.c
839 F: include/linux/perf/arm_pmu.h
8294 T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
8304 F: tools/perf/
10883 T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
DCREDITS834 E: terry@perf.no.itg.telecom.com.au