• H
    tracing: Don't trace kernel thread syscalls · cc3b13c1
    Hendrik Brueckner 提交于
    Kernel threads don't call syscalls using the sysenter/sysexit
    path. Instead they directly call the sys_* or do_* functions
    that implement the syscalls inside the kernel.
    
    The current syscall tracepoints only bind the sysenter/sysexit
    path, then it has no effect to trace the kernel thread calls
    to syscalls in that path.
    Setting the TIF_SYSCALL_TRACEPOINT flag is then useless for these.
    
    Actually there is only one case when a kernel thread can reach the
    usual syscall exit tracing path: when we create a kernel thread, the
    child comes to ret_from_fork and is the fork() return is then traced.
    But this information alone is useless, then we don't want to set the
    TIF flags for these threads.
    
    Kernel threads have task_struct->mm set to NULL.
    (Thanks to Heiko for that hint ;-)
    The idea is then to check the mm field in syscall_regfunc() and
    set the flag accordingly.
    Signed-off-by: NHendrik Brueckner <brueckner@linux.vnet.ibm.com>
    Cc: Jason Baron <jbaron@redhat.com>
    Cc: Frederic Weisbecker <fweisbec@gmail.com>
    Cc: Ingo Molnar <mingo@elte.hu>
    Cc: Lai Jiangshan <laijs@cn.fujitsu.com>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
    Cc: Jiaying Zhang <jiayingz@google.com>
    Cc: Martin Bligh <mbligh@google.com>
    Cc: Li Zefan <lizf@cn.fujitsu.com>
    Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
    Cc: Paul Mundt <lethal@linux-sh.org>
    Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
    Cc: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
    LKML-Reference: <20090825160237.GG4639@cetus.boeblingen.de.ibm.com>
    Signed-off-by: NFrederic Weisbecker <fweisbec@gmail.com>
    cc3b13c1
tracepoint.c 15.3 KB