From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Li Zefan <lizf@cn.fujitsu.com>,
Masami Hiramatsu <mhiramat@redhat.com>,
Jason Baron <jbaron@redhat.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH 2/2] tracing: Document HAVE_FTRACE_SYSCALLS needs
Date: Sat, 19 Sep 2009 09:29:09 +0200 [thread overview]
Message-ID: <20090919072908.GB5226@nowhere> (raw)
In-Reply-To: <20090919072827.GD15292@elte.hu>
On Sat, Sep 19, 2009 at 09:28:27AM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > On Sat, Sep 19, 2009 at 09:17:12AM +0200, Ingo Molnar wrote:
> > >
> > > * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> > >
> > > > Document the arch needed requirements to get the support for syscalls
> > > > tracing.
> > > >
> > > > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> > > > Cc: Ingo Molnar <mingo@elte.hu>
> > > > Cc: Steven Rostedt <rostedt@goodmis.org>
> > > > Cc: Li Zefan <lizf@cn.fujitsu.com>
> > > > Cc: Masami Hiramatsu <mhiramat@redhat.com>
> > > > Cc: Jason Baron <jbaron@redhat.com>
> > > > Cc: Lai Jiangshan <laijs@cn.fujitsu.com>
> > > > Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
> > > > Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> > > > Cc: Paul Mundt <lethal@linux-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
> >
> > Ah, that has been renamed HAVE_SYSCALL_TRACEPOINTS recently. What do
> > you prefer? A delta patch or a rebase?
>
> We need the acks from Martin/Heiko so lets wait for that and do a new
> tree then?
>
> Ingo
Ok.
next prev parent reply other threads:[~2009-09-19 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 5:39 [GIT PULL] tracing/syscalls: Arch code shrinks, easier arch integration Frederic Weisbecker
2009-09-19 5:39 ` [PATCH 1/2] tracing: Move syscalls metadata handling from arch to core Frederic Weisbecker
2009-09-19 7:16 ` Ingo Molnar
2009-09-19 7:48 ` Heiko Carstens
2009-09-19 8:12 ` Frederic Weisbecker
2009-09-19 5:39 ` [PATCH 2/2] tracing: Document HAVE_FTRACE_SYSCALLS needs Frederic Weisbecker
2009-09-19 7:17 ` Ingo Molnar
2009-09-19 7:22 ` Frederic Weisbecker
2009-09-19 7:28 ` Ingo Molnar
2009-09-19 7:29 ` Frederic Weisbecker [this message]
2009-09-19 9:08 ` [GIT PULL v2] tracing/syscalls: Arch code shrinks, easier arch integration Frederic Weisbecker
2009-10-13 22:25 ` Frederic Weisbecker
2009-10-14 6:18 ` Ingo Molnar
2009-10-14 7:28 ` Heiko Carstens
2009-09-19 9:08 ` [PATCH 1/2 v2] tracing: Move syscalls metadata handling from arch to core Frederic Weisbecker
2009-09-19 9:08 ` [PATCH 2/2 v2] tracing: Document HAVE_SYSCALL_TRACEPOINTS needs Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090919072908.GB5226@nowhere \
--to=fweisbec@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jbaron@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox