[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 5 May 2008 07:30:57 -0400
From: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org, systemtap@...rces.redhat.com,
"Frank Ch. Eigler" <fche@...hat.com>
Subject: Re: System call instrumentation
* Ingo Molnar (mingo@...e.hu) wrote:
>
> * Mathieu Desnoyers <mathieu.desnoyers@...ymtl.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
Ideally, I'd like to have this kind of high-level information :
event name : kernel syscall
syscall name : open
arg1 (%s) : "somefile" <-----
arg2 (%d) : flags
arg3 (%d) : mode
However, "somefile" has to be read from userspace. With the protection
involved, it would cause a performance impact to read it a second time
rather than tracing the string once it's been copied to kernel-space.
Mathieu
--
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists