This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Linux Trace terminology - feedback requested
- From: Richard J Moore <richardj_moore at uk dot ibm dot com>
- To: Li Guanglei <guanglei at cn dot ibm dot com>
- Cc: CE Linux Developers List <celinux-dev at tree dot celinuxforum dot org>, ltt-dev <ltt-dev at shafik dot org>, Tohru Nojiri <nojiri at sdl dot hitachi dot co dot jp>, systemtap <systemtap at sourceware dot org>, Tim Bird <tim dot bird at am dot sony dot com>
- Date: Fri, 19 May 2006 11:09:26 +0100
- Subject: Re: Linux Trace terminology - feedback requested
- Sensitivity:
systemtap-owner@sourceware.org wrote on 19/05/2006 03:55:39:
> Tim Bird ??:
>
> > I'm working on coordinating ...
>
> In LKET, we have some slight differences, listed below:
> >
> > Here is my first attempt:
> >
> > * event - an instruction location or system state at a specific
> point in time
> > * trace point - a location in the traced software, where an event
> is "emitted"
And as matter of semantics: point: trace point is better specified as
trace-point or tracepoint;
similarly for probe point; since these terms do not refer to "points" in
general.
> I called it "probe point". But "trace point" emphasizes more about
> "tracing".
> > * trace log - location where trace data is stored long-term
> > Does your tracing system use different terms for any of the above?
> > If so, what are they?
> >
>
> * event hook - refers to the (trace point definition)/(corresponding
> trace handler) in the *tracing* software for a specific event.
>
> * trace handler(probe handler) - The codes to be executed when a
> trace point is hit.
>
>