From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: ltt-dev@lists.casi.polymtl.ca
Cc: linux-kernel@vger.kernel.org
Subject: LTTng 0.10-pre57 for linux 2.6.26-rc9 (with userspace tracing for x86)
Date: Fri, 11 Jul 2008 11:19:06 -0400 [thread overview]
Message-ID: <20080711151905.GA13558@Krystal> (raw)
Hi,
Here is a new release of LTTng for the 2.6.26-rc9 kernel, which
introduces :
- The tracepoints infrastructure.
- Architecture independent markers converted to tracepoints.
- Re-introduction of userspace tracing, only for x86 for now. Allows to
do boot-time tracing (such as tracing the init process). Adds 2 system
calls : sys_marker (marker registration) and sys_trace (tracing per
se). The type support is currently limited : strings are formatted in
userspace and sent to the kernel for logging under the event
"userspace_string". I am doing this simple implementation to get the
feature in until I have time to think more carefully about namespacing
issues, typing and 32/64 bits processes in 64 bits architectures.
Please consider this last feature experimental. Review and testing is
welcome. The userspace linker script and library needed to perform
userspace tracing, as well as some sample code and Makefile, are
available in the svn repository at
http://ltt.polymtl.ca/svn/markers-userspace/
Ports of the linker script, kernel-api.h (which should be
per-architecture) and of markers-userspace-x86.patch to other
architectures are welcome.
As always, please follow the compatibility list and the quickstart guide
located at :
http://ltt.polymtl.ca/svn/ltt/branches/poly/doc/developer/lttng-lttv-compatibility.html
http://ltt.polymtl.ca/svn/ltt/branches/poly/QUICKSTART
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2008-07-11 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 15:19 Mathieu Desnoyers [this message]
2008-07-11 18:31 ` [ltt-dev] LTTng 0.10-pre58 for linux 2.6.26-rc9 (with userspace tracing for x86) Mathieu Desnoyers
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=20080711151905.GA13558@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
/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