Messages in this thread Patch in this message | | | Date | Mon, 16 Mar 2009 08:19:07 GMT | From | Frederic Weisbecker <> | Subject | [tip:tracing/syscalls] tracing/syscalls: select kallsysms |
| |
Commit-ID: 0ea1c4156bf9e2eb370cc5c6fa6eb112bd844dec Gitweb: http://git.kernel.org/tip/0ea1c4156bf9e2eb370cc5c6fa6eb112bd844dec Author: Frederic Weisbecker <fweisbec@gmail.com> AuthorDate: Sun, 15 Mar 2009 22:10:38 +0100 Commit: Ingo Molnar <mingo@elte.hu> CommitDate: Mon, 16 Mar 2009 09:13:17 +0100
tracing/syscalls: select kallsysms
Syscall tracing must select kallsysms.
The arch code builds a table to find the syscall metadata by syscall number. It needs the syscalls names resolution from the symbol table to know which name found on the syscalls metadatas match a function pointer from the arch sys_call_table.
Reported-by: Andrew Morton <akpm@linux-foundation.org> Reported-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com> LKML-Reference: <1237151439-6755-4-git-send-email-fweisbec@gmail.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
--- kernel/trace/Kconfig | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index 95a0ad1..b0a46f8 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig @@ -182,6 +182,7 @@ config FTRACE_SYSCALLS bool "Trace syscalls" depends on HAVE_FTRACE_SYSCALLS select TRACING + select KALLSYMS help Basic tracer to catch the syscall entry and exit events.
| |