2011/3/27 David Ahern <[email protected]>: > > > On 03/26/11 10:13, zhao bao wrote: >> Follow your guide, I git the latest kernel and compiled the perf tools >> , then perf script works. >> But I found the outputed address is instruction address, not the >> address caused the page fault. Can I get these addresses with perf >> tool? >> [root@localhost lab]# /root/bin/perf script >> hello 30242 [000] 48324.304652: page-faults: >> c05b6d35 clear_user ([kernel.kallsyms]) >> hello 30242 [000] 48324.304684: page-faults: >> c05b6d35 clear_user ([kernel.kallsyms]) >> hello 30242 [000] 48324.304701: page-faults: >> c05b68a0 __copy_to_user_ll ([kernel.kallsyms]) >> hello 30242 [000] 48324.304746: page-faults: >> 870 _start (/lib/ld-2.13.so) >> hello 30242 [000] 48324.304750: page-faults: >> 4920 _dl_start (/lib/ld-2.13.so) >> hello 30242 [000] 48324.304753: page-faults: >> 17acb __i686.get_pc_thunk.bx (/lib/ld-2.13.so) >> hello 30242 [000] 48324.304755: page-faults: >> 4939 _dl_start (/lib/ld-2.13.so) >> hello 30242 [000] 48324.304765: page-faults: >> a790 _dl_setup_hash (/lib/ld-2.13.so) >> hello 30242 [000] 48324.304768: page-faults: >> 14480 _dl_sysdep_start (/lib/ld-2.13.so) >> hello 30242 [000] 48324.304771: page-faults: >> 14560 _dl_sysdep_start (/lib/ld-2.13.so) >> hello 30242 [000] 48324.304774: page-faults: >> 159e0 brk (/lib/ld-2.13.so) > > Without callchains it shows the IP when the event triggered. If you want > more detail try adding -g to perf-record to get callchains. > Thanks for your kind reply.I am sorry for misleading you.
The address I want is the value stored in X86 CR2 register when page fault occurs, Does perf provide these information? Another question. I find a new utility called 'trace' mentioned in http://lwn.net/Articles/415728/ which provides I want (trace report -p). But I git the tip tree, and make -j install in tools/perf directory, I couldn't find trace utility. Where is the trace utility? -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
