Re: [GIT PULL] tracing: Syscalls trace events + perf support

[Jason Baron]

On Wed, Aug 12, 2009 at 04:29:17PM +0200, Ingo Molnar wrote:
> * Jason Baron <jbaron@xxxxxxxxxx> wrote:
> 
> > On Wed, Aug 12, 2009 at 01:14:36PM +0200, Ingo Molnar wrote:
> 
> > > another thing: could we please also have a generic, highlevel 
> > > tracepoint (in addition to the specific tracepoints) that 
> > > enumerates the raw syscall Nr and the parameters it gets - in a 
> > > single tracepoint?
> > 
> > The specific tracepoints, are all layered on 2 (entry, exit) 
> > generic tracepoints already. So this shouldn't be too hard...The 
> > parameters it gets might be tricky, since there are a variable 
> > number b/w different syscalls?
> 
> We should just list all ~6 of them. It's up to the sampling entity 
> to decide which ones (if any) is relevant.
> 
> At least on x86 the syscall arguments will always have a value when 
> the syscall entry code is called. (they are in GP registers)
> 
> 	Ingo

ok, makes sense. I'll add to the todo list.

-Jason


--
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/