| perf-trace.txt (598d02c5a07b60e5c824184cdaf697b70f3c452a) | perf-trace.txt (e281a9606d7073c517f2571e83faaff029ddc1cf) |
|---|---|
| 1perf-trace(1) 2============= 3 4NAME 5---- 6perf-trace - strace inspired tool 7 8SYNOPSIS --- 98 unchanged lines hidden (view full) --- 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 | 1perf-trace(1) 2============= 3 4NAME 5---- 6perf-trace - strace inspired tool 7 8SYNOPSIS --- 98 unchanged lines hidden (view full) --- 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 |
| 115--syscalls:: 116 Trace system calls. This options is enabled by default. 117 |
|
| 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; --- 9 unchanged lines hidden (view full) --- 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 | 118PAGEFAULTS 119---------- 120 121When tracing pagefaults, the format of the trace is as follows: 122 123<min|maj>fault [<ip.symbol>+<ip.offset>] => <addr.dso@addr.offset> (<map type><addr level>). 124 125- min/maj indicates whether fault event is minor or major; --- 9 unchanged lines hidden (view full) --- 135time it took for fault to be handled! 136 137When --verbose specified, perf trace tries to print all available information 138for both IP and fault address in the form of dso@symbol+offset. 139 140EXAMPLES 141-------- 142 |
| 143Trace only major pagefaults: 144 145 $ perf trace --no-syscalls -F 146 |
|
| 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 149SEE ALSO 150-------- 151linkperf:perf-record[1], linkperf:perf-script[1] | 147Trace syscalls, major and minor pagefaults: 148 149 $ perf trace -F all 150 151 1416.547 ( 0.000 ms): python/20235 majfault [CRYPTO_push_info_+0x0] => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0@0x61be0 (x.) 152 153 As you can see, there was major pagefault in python process, from 154 CRYPTO_push_info_ routine which faulted somewhere in libcrypto.so. 155 156SEE ALSO 157-------- 158linkperf:perf-record[1], linkperf:perf-script[1] |