This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: System call instrumentation


* Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:

> > hm, i'm not sure about this. I've implemented system call tracing in 
> > -rt [embedded in the latency tracer] and it only needed changes in 
> > entry.S, not in every system call site. Now, granted, that tracer 
> > was simpler than what LTTng tries to do, but do we _really_ need 
> > more complexity? A trace point that simply expresses:
> > 
> >    sys_call_event(int sysno, long param1, long param2, long param3,
> >                              long param4, long param5, long param6);
> > 
> 
> That would work for all system calls that doesn't have parameters like 
> "const char __user *filename".

what's the problem with them? Do you want to follow those parameters?

	Ingo


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]