We'll need to find a better way to instrument ARM-specific system calls
located at a far offset from the standard systems calls. A 16MB
lttng-modules kernel module is really not acceptable.
Removing this instrumentation for now. sys_set_tls will appear as
sys_unknown.
Fixes #472
CC: Ryan Kyser <Ryan.Kyser@jci.com>
Ref: http://lists.lttng.org/pipermail/lttng-dev/2013-April/019990.html
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
#define OVERRIDE_TABLE_32_sys_arm_fadvise64_64
#define OVERRIDE_TABLE_32_sys_sync_file_range2
#define OVERRIDE_TABLE_32_sys_arm_fadvise64_64
#define OVERRIDE_TABLE_32_sys_sync_file_range2
-#define OVERRIDE_TABLE_32_sys_set_tls
#ifndef CREATE_SYSCALL_TABLE
#ifndef CREATE_SYSCALL_TABLE
-SC_TRACE_EVENT(sys_set_tls,
- TP_PROTO(unsigned int tid, unsigned long tls),
- TP_ARGS(tid, tls),
- TP_STRUCT__entry(
- __field(unsigned int, tid)
- __field_hex(unsigned int, tls)),
- TP_fast_assign(
- tp_assign(tid, tid)
- tp_assign(tls, tls)),
- TP_printk()
-)
-
#else /* CREATE_SYSCALL_TABLE */
#define OVVERRIDE_TABLE_32_sys_mmap
#else /* CREATE_SYSCALL_TABLE */
#define OVVERRIDE_TABLE_32_sys_mmap
TRACE_SYSCALL_TABLE(sys_arm_fadvise64_64, sys_arm_fadvise64_64, 270, 4)
#define OVERRIDE_TABLE_32_sys_sync_file_range2
TRACE_SYSCALL_TABLE(sys_sync_file_range2, sys_sync_file_range2, 341, 4)
TRACE_SYSCALL_TABLE(sys_arm_fadvise64_64, sys_arm_fadvise64_64, 270, 4)
#define OVERRIDE_TABLE_32_sys_sync_file_range2
TRACE_SYSCALL_TABLE(sys_sync_file_range2, sys_sync_file_range2, 341, 4)
-#define OVERRIDE_TABLE_32_sys_set_tls
-TRACE_SYSCALL_TABLE(sys_set_tls, sys_set_tls, 0xf0005, 2)
-
#endif /* CREATE_SYSCALL_TABLE */
#endif /* CREATE_SYSCALL_TABLE */