Re: [RFC][PATCH 2/2] tracing/x86: basic implementation of syscalltracing for x86-64

From: Mathieu Desnoyers
Date: Fri Mar 13 2009 - 12:50:40 EST


* Ingo Molnar (mingo@xxxxxxx) wrote:
>
> * Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx> wrote:
>
> > * Frederic Weisbecker (fweisbec@xxxxxxxxx) wrote:
> >
> > > Provide the ptrace hooks and arch specific syscall numbers
> > > to ftrace arch indepedant syscall numbers. For now it only
> > > supports 4 syscalls to provide an example.
> > >
> >
> > Hi Frederic,
> >
> > I already have the equivalent TIF_KERNEL_TRACE flag in my
> > LTTng tree added to every Linux architecture. You might want
> > to re-use this work rather than re-doing this. I don't mind
> > changing the flag name.
>
> Yeah. Note that the TIF bits are just one part - there are other
> bits needed for HAVE_FTRACE_SYSCALLS arch support.
>
> Also, i'd eventually expect the TIF bits to be converted to a
> tracehook callback, not spread it to other architectures.
>

The nice part about the TIF bit is that it permits adding this syscall
tracing feature without increasing the size of the thread_info struct
nor adding any extra tests in entry.S. Does the tracehook callback have
these features ?

Mathieu

> Ingo

--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/