From: Richard J Moore <richardj_moore@uk.ibm.com>
To: Li Guanglei <guanglei@cn.ibm.com>
Cc: CE Linux Developers List <celinux-dev@tree.celinuxforum.org>,
ltt-dev <ltt-dev@shafik.org>,
Tohru Nojiri <nojiri@sdl.hitachi.co.jp>,
systemtap <systemtap@sourceware.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: Linux Trace terminology - feedback requested
Date: Fri, 19 May 2006 10:40:00 -0000 [thread overview]
Message-ID: <OF5560A453.48D2EB7A-ON41257173.00378C3D-41257173.0037CBE3@uk.ibm.com> (raw)
In-Reply-To: <446D33AB.2010207@cn.ibm.com>
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.
>
>
next prev parent reply other threads:[~2006-05-19 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 22:23 Tim Bird
2006-05-19 2:56 ` Li Guanglei
2006-05-19 10:40 ` Richard J Moore [this message]
2006-05-19 8:56 ` Richard J Moore
2006-05-19 14:02 ` [ltt-dev] " Michel Dagenais
2006-05-19 15:12 ` Frank Ch. Eigler
2006-05-19 16:12 ` Michel Dagenais
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF5560A453.48D2EB7A-ON41257173.00378C3D-41257173.0037CBE3@uk.ibm.com \
--to=richardj_moore@uk.ibm.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=guanglei@cn.ibm.com \
--cc=ltt-dev@shafik.org \
--cc=nojiri@sdl.hitachi.co.jp \
--cc=systemtap@sourceware.org \
--cc=tim.bird@am.sony.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).