Skip to contentSkip to conversation

tracing: Fix syscall tracing on !HAVE_FTRACE_SYSCALLS architectures

tip:tracing/core tip-bot for Ingo Molnar 1 participant 1 message Aug 13, 2009 Tracing

lore
Share & tools
lore
#0 lore raw
Commit-ID:  60d970c254b95ec7a0fc4c590b510253987b64a0
Gitweb:     http://git.kernel.org/tip/60d970c254b95ec7a0fc4c590b510253987b64a0
Author:     Ingo Molnar <[email protected]>
AuthorDate: Thu, 13 Aug 2009 23:37:26 +0200
Committer:  Ingo Molnar <[email protected]>
CommitDate: Thu, 13 Aug 2009 23:38:20 +0200

tracing: Fix syscall tracing on !HAVE_FTRACE_SYSCALLS architectures

The new syscall_regfunc()/unregfunc() functions rely on the existence of TIF_SYSCALL_FTRACE - but that TIF flag is only offered by HAVE_FTRACE_SYSCALLS.

Cc: Frederic Weisbecker <[email protected]>
Cc: Jason Baron <[email protected]>
Cc: Steven Rostedt <[email protected]>
Cc: Peter Zijlstra <[email protected]>
LKML-Reference: <new-submission>

---
 kernel/tracepoint.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
kernel/tracepoint.c +3 -0
index 070a42b..35dd27a 100644
@@ -579,6 +579,8 @@ __initcall(init_tracepoints);
 
 #endif /* CONFIG_MODULES */
 
+#ifdef CONFIG_FTRACE_SYSCALLS
+
 static DEFINE_MUTEX(regfunc_mutex);
 static int sys_tracepoint_refcount;
 
@@ -615,3 +617,4 @@ void syscall_unregfunc(void)
 	}
 	mutex_unlock(&regfunc_mutex);
 }
+#endif