perf-trace.txt 4.5 KB
Newer Older
A
Arnaldo Carvalho de Melo 已提交
1 2 3 4 5 6 7 8 9 10 11
perf-trace(1)
=============

NAME
----
perf-trace - strace inspired tool

SYNOPSIS
--------
[verse]
'perf trace'
D
David Ahern 已提交
12
'perf trace record'
A
Arnaldo Carvalho de Melo 已提交
13 14 15 16 17 18 19

DESCRIPTION
-----------
This command will show the events associated with the target, initially
syscalls, but other system events like pagefaults, task lifetime events,
scheduling events, etc.

D
David Ahern 已提交
20 21 22
This is a live mode tool in addition to working with perf.data files like
the other perf tools. Files can be generated using the 'perf record' command
but the session needs to include the raw_syscalls events (-e 'raw_syscalls:*').
23
Alternatively, 'perf trace record' can be used as a shortcut to
D
David Ahern 已提交
24 25 26 27
automatically include the raw_syscalls events when writing events to a file.

The following options apply to perf trace; options to perf trace record are
found in the perf record man page.
A
Arnaldo Carvalho de Melo 已提交
28 29 30 31

OPTIONS
-------

32
-a::
A
Arnaldo Carvalho de Melo 已提交
33 34 35
--all-cpus::
        System-wide collection from all CPUs.

36 37 38
-e::
--expr::
	List of events to show, currently only syscall names.
39 40
	Prefixing with ! shows all syscalls but the ones specified.  You may
	need to escape it.
41

42 43 44 45
-o::
--output=::
	Output file name.

A
Arnaldo Carvalho de Melo 已提交
46 47 48 49
-p::
--pid=::
	Record events on existing process ID (comma separated list).

50
-t::
A
Arnaldo Carvalho de Melo 已提交
51 52 53
--tid=::
        Record events on existing thread ID (comma separated list).

54
-u::
A
Arnaldo Carvalho de Melo 已提交
55 56 57
--uid=::
        Record events in threads owned by uid. Name or number.

58 59 60
--filter-pids=::
	Filter out events for these pids and for 'trace' itself (comma separated list).

61 62 63 64
-v::
--verbose=::
        Verbosity level.

65
-i::
A
Arnaldo Carvalho de Melo 已提交
66 67 68
--no-inherit::
	Child tasks do not inherit counters.

69
-m::
A
Arnaldo Carvalho de Melo 已提交
70
--mmap-pages=::
71 72 73
	Number of mmap data pages (must be a power of two) or size
	specification with appended unit character - B/K/M/G. The
	size is rounded up to have nearest pages power of two value.
A
Arnaldo Carvalho de Melo 已提交
74

75
-C::
A
Arnaldo Carvalho de Melo 已提交
76 77 78 79 80 81
--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), Events are captured only when
the thread executes on the designated CPUs. Default is to monitor all CPUs.

82 83 84
--duration:
	Show only events that had a duration greater than N.M ms.

85 86 87
--sched:
	Accrue thread runtime and provide a summary at the end of the session.

88 89 90 91
-i
--input
	Process events from a given perf data file.

92 93 94 95
-T
--time
	Print full timestamp rather time relative to first sample.

96 97 98
--comm::
        Show process COMM right beside its ID, on by default, disable with --no-comm.

D
David Ahern 已提交
99
-s::
100
--summary::
D
David Ahern 已提交
101 102 103 104 105 106 107
	Show only a summary of syscalls by thread with min, max, and average times
    (in msec) and relative stddev.

-S::
--with-summary::
	Show all syscalls followed by a summary by thread with min, max, and
    average times (in msec) and relative stddev.
108

109 110 111 112
--tool_stats::
	Show tool stats such as number of times fd->pathname was discovered thru
	hooking the open syscall return + vfs_getname or via reading /proc/pid/fd, etc.

113 114 115 116 117
-F=[all|min|maj]::
--pf=[all|min|maj]::
	Trace pagefaults. Optionally, you can specify whether you want minor,
	major or all pagefaults. Default value is maj.

118 119 120
--syscalls::
	Trace system calls. This options is enabled by default.

121 122 123
--event::
	Trace other events, see 'perf list' for a complete list.

124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148
PAGEFAULTS
----------

When tracing pagefaults, the format of the trace is as follows:

<min|maj>fault [<ip.symbol>+<ip.offset>] => <addr.dso@addr.offset> (<map type><addr level>).

- min/maj indicates whether fault event is minor or major;
- ip.symbol shows symbol for instruction pointer (the code that generated the
  fault); if no debug symbols available, perf trace will print raw IP;
- addr.dso shows DSO for the faulted address;
- map type is either 'd' for non-executable maps or 'x' for executable maps;
- addr level is either 'k' for kernel dso or '.' for user dso.

For symbols resolution you may need to install debugging symbols.

Please be aware that duration is currently always 0 and doesn't reflect actual
time it took for fault to be handled!

When --verbose specified, perf trace tries to print all available information
for both IP and fault address in the form of dso@symbol+offset.

EXAMPLES
--------

149 150 151 152
Trace only major pagefaults:

 $ perf trace --no-syscalls -F

153 154 155 156 157 158 159 160 161
Trace syscalls, major and minor pagefaults:

 $ perf trace -F all

  1416.547 ( 0.000 ms): python/20235 majfault [CRYPTO_push_info_+0x0] => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0@0x61be0 (x.)

  As you can see, there was major pagefault in python process, from
  CRYPTO_push_info_ routine which faulted somewhere in libcrypto.so.

A
Arnaldo Carvalho de Melo 已提交
162 163 164
SEE ALSO
--------
linkperf:perf-record[1], linkperf:perf-script[1]