syscall vs kernel.syscall

Li Guanglei guanglei@cn.ibm.com
Wed Jun 21 13:20:00 GMT 2006


Hi,

  I found some syscall probe names in current syscalls.stp are started
with "kernel.syscall." ,e.g probe kernel.syscall.madvise, although
most syscall probe aliases are started with "syscall.". Are those
syscalls started with "kernel.syscall" omitted during past syscalls
tapsets changes?

  I think it's better if all syscall probes are started with
"syscall." to make the name convention consistent and "probe
syscall.*" can trace all syscalls.

- Guanglei



More information about the Systemtap mailing list