get the mapping of <key, syscallname>

Hien Nguyen hien@us.ibm.com
Mon May 15 16:39:00 GMT 2006


On Sat, 2006-05-13 at 15:18 +0800, Li Guanglei wrote:

> 
> But it still has one issue. e.g, I tried to use:
> probe syscall.* { ... } to trace all system calls on ppc64. But it 
> failed since sys64_time(defined in SystemTap's ppc64/syscall.stp) is 
> removed from  2.6.16.5/ppc64. I think this issues has been addressed 
> in bug 2645.

For the time being,  I would use the kernel_v preprocessor. I fact there
are a few of them in the ppc64/syscall.stp. 
> 
> If this bug #2645 is resolved , then I think I can use the syscall.stp 
> tapsets shipped with SystemTap. Another advantage of using it is that 
> I can simply use the $name instead of getting it using lines of codes.

Another advantage is when more people start using syscalls tapset we
will get more feedback (bug reports).




More information about the Systemtap mailing list