This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: is systemtap's language more complicated than needed.
Hi -
varap wrote:
> [...] Although we wont be monitoring syscalls in the application
> systemcall tapset is correct in referring to kernel.syscall rather
> than just syscall [...]
Actually, syscall.* is the proper name - just like our many other
aliases that don't bother with a prefix (e.g., LKET, I/O, signals,
....) Any instances of kernel.syscall that still remain constitute
unfinished work from an old bug. However, a brief grep shows that in
fact no such instances still remain in CVS, except in one man page
where it was used for syntactic illustration only.
- FChE