Date: Wed, 18 Mar 2009 17:44:33 +0100
From: Ingo Molnar <mingo@elte.hu>
To: William Cohen <wcohen@redhat.com>, Steven Rostedt <rostedt@goodmis.org>,
       =?iso-8859-1?Q?Fr=E9d=E9ric?= 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
Message-ID: <20090318164433.GA31315@elte.hu>
References: <49C122DF.7020803@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49C122DF.7020803@redhat.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1133
Lines: 28


* 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/