* syscall vs kernel.syscall
@ 2006-06-21 13:20 Li Guanglei
0 siblings, 0 replies; only message in thread
From: Li Guanglei @ 2006-06-21 13:20 UTC (permalink / raw)
To: systemtap
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-06-21 13:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-06-21 13:20 syscall vs kernel.syscall Li Guanglei
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).