| perf-trace.txt (b7d3622a39fde7658170b7f3cf6c6889bb8db30d) | perf-trace.txt (598d02c5a07b60e5c824184cdaf697b70f3c452a) |
|---|---|
| 1perf-trace(1) 2============= 3 4NAME 5---- 6perf-trace - strace inspired tool 7 8SYNOPSIS --- 93 unchanged lines hidden (view full) --- 102--with-summary:: 103 Show all syscalls followed by a summary by thread with min, max, and 104 average times (in msec) and relative stddev. 105 106--tool_stats:: 107 Show tool stats such as number of times fd->pathname was discovered thru 108 hooking the open syscall return + vfs_getname or via reading /proc/pid/fd, etc. 109 | 1perf-trace(1) 2============= 3 4NAME 5---- 6perf-trace - strace inspired tool 7 8SYNOPSIS --- 93 unchanged lines hidden (view full) --- 102--with-summary:: 103 Show all syscalls followed by a summary by thread with min, max, and 104 average times (in msec) and relative stddev. 105 106--tool_stats:: 107 Show tool stats such as number of times fd->pathname was discovered thru 108 hooking the open syscall return + vfs_getname or via reading /proc/pid/fd, etc. 109 |
| 110-F=[all|min|maj]:: 111--pf=[all|min|maj]:: 112 Trace pagefaults. Optionally, you can specify whether you want minor, 113 major or all pagefaults. Default value is maj. 114 115PAGEFAULTS 116---------- 117 118When tracing pagefaults, the format of the trace is as follows: 119 120<min|maj>fault [<ip.symbol>+<ip.offset>] => <addr.dso@addr.offset> (<map type><addr level>). 121 122- min/maj indicates whether fault event is minor or major; 123- ip.symbol shows symbol for instruction pointer (the code that generated the 124 fault); if no debug symbols available, perf trace will print raw IP; 125- addr.dso shows DSO for the faulted address; 126- map type is either 'd' for non-executable maps or 'x' for executable maps; 127- addr level is either 'k' for kernel dso or '.' for user dso. 128 129For symbols resolution you may need to install debugging symbols. 130 131Please be aware that duration is currently always 0 and doesn't reflect actual 132time it took for fault to be handled! 133 134When --verbose specified, perf trace tries to print all available information 135for both IP and fault address in the form of dso@symbol+offset. 136 137EXAMPLES 138-------- 139 140Trace syscalls, major and minor pagefaults: 141 142 $ perf trace -F all 143 144 1416.547 ( 0.000 ms): python/20235 majfault [CRYPTO_push_info_+0x0] => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0@0x61be0 (x.) 145 146 As you can see, there was major pagefault in python process, from 147 CRYPTO_push_info_ routine which faulted somewhere in libcrypto.so. 148 |
|
| 110SEE ALSO 111-------- 112linkperf:perf-record[1], linkperf:perf-script[1] | 149SEE ALSO 150-------- 151linkperf:perf-record[1], linkperf:perf-script[1] |