[PATCH] tapsetset/memory.stp

William Cohen wcohen@redhat.com
Tue Apr 1 19:49:00 GMT 2014


When experimenting with the pfaults.stp systemtap example on Fedora 19 I noticed that pfaults failed because the probe vm.fault points. There are similar failure listed in dejazilla:

https://web.elastic.org/~dejazilla/view.php?_offset=0&_limit=100&_offset=0&summary=%3D%27%3C201404011556.s31FuPfn021470%40elastic.org%3E%27&age=&rg=&tool=%3D%27systemtap%27&variant=%3D%27x86_64-unknown-linux-gnu%27&versions=&testcase=&result=%3D%27FAIL%27

The attached patch attempts to instrument the exported function handle_mm_fault rather than the internal function __handle_mm_fault.  The internal function tends to get inlined and some arguments are not available causing the pfault.stp not to build. Does this look reasonable?

-Will
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pagefault.patch
Type: text/x-patch
Size: 1053 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/systemtap/attachments/20140401/49f98cf3/attachment.bin>


More information about the Systemtap mailing list