get the mapping of <key, syscallname>
Frank Ch. Eigler
fche@redhat.com
Fri May 12 16:12:00 GMT 2006
Hi -
> > Why not use the "name" variable set by the syscalls tapset?
>
> LKET does not currently use the syscall tapset because it doesnt use the
> extra information that this tapset collects from each systemcall. [...]
But, due to the optimization pass in the translator, only that portion
of the information actually *used* by your script is actually
collected. Please try it out (check out stap -p2 or -p3 output to
confirm).
> [...] Its not just the string printing that's costly, its also
> searching the system call name with in CONTEXT->probe_point. [...]
Rolling your own code to manually scan through "probe_point" is not
really necessary or appropriate. There is a "probefunc()" function
you can use for now.
- FChE
More information about the Systemtap
mailing list