From: William Cohen <wcohen@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Documenting kernel tracepoints
Date: Wed, 18 Mar 2009 12:35:43 -0400 [thread overview]
Message-ID: <49C122DF.7020803@redhat.com> (raw)
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?
-Will
next reply other threads:[~2009-03-18 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 16:35 William Cohen [this message]
2009-03-18 16:44 ` Documenting kernel tracepoints Ingo Molnar
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=49C122DF.7020803@redhat.com \
--to=wcohen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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