This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Problems in syscall.stp and syscall2.stp
- From: Wenji Huang <wenji dot huang at oracle dot com>
- To: SystemTAP <systemtap at sources dot redhat dot com>
- Date: Tue, 07 Aug 2007 17:19:28 +0800
- Subject: Problems in syscall.stp and syscall2.stp
- References: <46B78443.2070508@redhat.com>
Hi,
Found there are two problems in syscall.stp and syscall2.stp.
1. probe point related to kernel config, such as sys_quotactl, valid
in CONFIG_QUOTA=y.
Moreover some test scripts dependent on kernel config.
Currently, no statement to handle that.
***Suggestion: add config read functions.
%(kernel_config(CONFIG_QUOTA)=="y" %?)
xxxxxxx
%)
But should enable Kernel .config support and get the detailed
config information from file /proc/config.gz.
2. probe point related to architecture, such as compat_do_execve and
compat_sys_semtimedop are functions for providing 32 bit
compatibility code in 64 bit systems. So, they exist in x86_64, s390x, etc.
I tried to defined them using condition statement:
%(arch == "x86_64" || arch == "s390x" %?
probe syscall.compat_do_execve =
kernel.functions("compat_do_execve")
But report syntax error, seems this kind of writing not supported.
Also, Is there list for architectures classified by 32/64 systems?
***One suggested solution is to move these probes into
corresponding directories. of course keep same copy.
Regards,
Wenji