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] |
Li Guanglei <guanglei@cn.ibm.com> writes:LKET does not currently use the syscall tapset because it doesnt use the extra information that this tapset collects from each systemcall. In order to improve performance, we keep the system call trace as simple as possible.
One of my tapsets will log the syscall name got from CONTEXT->probe_point. [...]
Why not use the "name" variable set by the syscalls tapset?
[...] I want to log the key of syscall name, and later the post-processing app in user space will figure out the syscall name represented by corresponding keys. [...]
As does Martin, I wonder if this is a good place to spend your
optimization energies. Anyway, one possibility is to have the
syscalls tapset also define a system call number variable.
- FChE
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |