From: Ingo Molnar <mingo@elte.hu>
To: "William Cohen" <wcohen@redhat.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Documenting kernel tracepoints
Date: Wed, 18 Mar 2009 17:44:33 +0100 [thread overview]
Message-ID: <20090318164433.GA31315@elte.hu> (raw)
In-Reply-To: <49C122DF.7020803@redhat.com>
* William Cohen <wcohen@redhat.com> wrote:
> There are a number of tracepoints in the latest kernels, but not
> much documentation on the tracepoints. If a very recent version
> of systemtap is available on the system, a list of the probe
> points can be obtained with:
>
> stap -p2 -e 'probe kernel.trace("*") {exit()}'|sort
>
> However, this only provides the names. It doesn't provide
> information about what information the probe point provides or the
> arguments available at the probe point.
>
> Currently, a number of kernel functions and structures are
> documented with embedded comments that are extracted with
> kernel-doc. Seems like it would be reasonable to extend this to
> support tracepoints. Any thoughts or comments about this approach?
FYI, in the latest tracing tree (targeted for 2.6.30) all
tracepoints show up under /debug/tracing/events/.
Ingo
next prev parent reply other threads:[~2009-03-18 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 16:35 Documenting kernel tracepoints William Cohen
2009-03-18 16:44 ` Ingo Molnar [this message]
2009-03-18 18:44 ` William Cohen
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=20090318164433.GA31315@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=wcohen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.