This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
resending due to improper mime type on the original
it would be simpler in most cases to probe syscalls that are easily trackable to pid's though this won't give a totally accurate of IO because of caching, but it is the easiest, and safest. When you go to lower level kernel interfaces it becomes difficult to attiribute actions with the pid that caused them.
James Dickens uadmin.blogspot.com
Currently Systemtap could make you able to trace all syscalls by pid, e.g: stap -e "probe addevent.syscall {} " -x pid to trace both entry & return of all syscalls or: stap -e "probe addevent.syscall {}" -c command
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |