Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754921AbZISHRT (ORCPT ); Sat, 19 Sep 2009 03:17:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753094AbZISHRS (ORCPT ); Sat, 19 Sep 2009 03:17:18 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:39095 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750901AbZISHRR (ORCPT ); Sat, 19 Sep 2009 03:17:17 -0400 Date: Sat, 19 Sep 2009 09:17:12 +0200 From: Ingo Molnar To: Frederic Weisbecker Cc: LKML , Steven Rostedt , Li Zefan , Masami Hiramatsu , Jason Baron , Lai Jiangshan , Heiko Carstens , Martin Schwidefsky , Paul Mundt Subject: Re: [PATCH 2/2] tracing: Document HAVE_FTRACE_SYSCALLS needs Message-ID: <20090919071712.GB15292@elte.hu> References: <1253338757-5918-1-git-send-email-fweisbec@gmail.com> <1253338757-5918-3-git-send-email-fweisbec@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1253338757-5918-3-git-send-email-fweisbec@gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Frederic Weisbecker wrote: > Document the arch needed requirements to get the support for syscalls > tracing. > > Signed-off-by: Frederic Weisbecker > Cc: Ingo Molnar > Cc: Steven Rostedt > Cc: Li Zefan > Cc: Masami Hiramatsu > Cc: Jason Baron > Cc: Lai Jiangshan > Cc: Heiko Carstens > Cc: Martin Schwidefsky > Cc: Paul Mundt > --- > Documentation/trace/ftrace-design.txt | 11 ++++++++++- > 1 files changed, 10 insertions(+), 1 deletions(-) > > diff --git a/Documentation/trace/ftrace-design.txt b/Documentation/trace/ftrace-design.txt > index 7003e10..04ab61c 100644 > --- a/Documentation/trace/ftrace-design.txt > +++ b/Documentation/trace/ftrace-design.txt > @@ -216,7 +216,16 @@ If you can't trace NMI functions, then skip this option. > HAVE_FTRACE_SYSCALLS > --------------------- > > -
> +You need very few things to get the syscalls tracing in an arch. > + > +- Have a NR_syscalls variable in that provides the number > + of syscalls supported by the arch. > +- Implement arch_syscall_addr() that resolves a syscall address from a > + syscall number. > +- Support the TIF_SYSCALL_TRACEPOINT thread flags > +- Put the trace_sys_enter() and trace_sys_exit() tracepoints calls from ptrace > + in the ptrace syscalls tracing path. > +- Tag this arch as HAVE_FTRACE_SYSCALLS. HAVE_FTRACE_SYSCALLS is not actually used anywhere. Ingo