linux-kernel - Re: [PATCH 2/2] tracing: Document HAVE_FTRACE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090919071712.GB15292@elte.hu>
Date:	Sat, 19 Sep 2009 09:17:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Li Zefan <lizf@...fujitsu.com>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Jason Baron <jbaron@...hat.com>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Paul Mundt <lethal@...ux-sh.org>
Subject: Re: [PATCH 2/2] tracing: Document HAVE_FTRACE_SYSCALLS needs


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> Document the arch needed requirements to get the support for syscalls
> tracing.
> 
> Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
> Cc: Ingo Molnar <mingo@...e.hu>
> Cc: Steven Rostedt <rostedt@...dmis.org>
> Cc: Li Zefan <lizf@...fujitsu.com>
> Cc: Masami Hiramatsu <mhiramat@...hat.com>
> Cc: Jason Baron <jbaron@...hat.com>
> Cc: Lai Jiangshan <laijs@...fujitsu.com>
> Cc: Heiko Carstens <heiko.carstens@...ibm.com>
> Cc: Martin Schwidefsky <schwidefsky@...ibm.com>
> Cc: Paul Mundt <lethal@...ux-sh.org>
> ---
>  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
>  ---------------------
>  
> -<details to be filled>
> +You need very few things to get the syscalls tracing in an arch.
> +
> +- Have a NR_syscalls variable in <asm/unistd.h> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/