From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: ltt-dev@lists.casi.polymtl.ca
Cc: linux-kernel@vger.kernel.org
Subject: [RELEASE/STATUS] LTTng 0.240 for kernel 2.6.36.2
Date: Wed, 5 Jan 2011 18:40:41 -0500 [thread overview]
Message-ID: <20110105234041.GA11813@Krystal> (raw)
LTTng, the Linux Trace Toolkit Next Generation, is a project that aims at
producing a highly efficient full system tracing solution. It is composed of
several components to allow tracing of the kernel, of userspace, trace viewing
and analysis and trace streaming. LTTng is open source software. It is being
actively developed with the community.
Changelog:
- Implement a user-space trace clock into a new clock_gettime() clock id.
(will be used by the next UST release). It will provide consistent timestamps
between userspace and kernel traces taken on a LTTng-enabled Linux kernel.
- Moved to stable kernel 2.6.36.2 (last LTTng release targeting 2.6.36.x,
moving on to 2.6.37 shortly)
Project Status:
- I am currently working on a LTTng redesign to better suit the need of Linux
distributions. The kernel-side work is very well advanced, and I'm now moving
on to the following steps: redesign lttd/lttctl/ltt-armall with a more
integrated approach (lttngtrace), and move LTTV to the new CTF (Common Trace
Format). I am keeping this redesign separate from the "stable" LTTng versions
for now, as it removes some of the LTTng-specific instrumentation to bring the
size of the patchset down to something more appealing to distributions.
The ongoing redesign is available in the lttng-modules git tree HEAD, but
depends on a reduced kernel tree LTTng patchset that I have not yet released.
Project website: http://lttng.org
Download link: http://lttng.org/content/download
(please refer to the LTTng Manual for installation instructions)
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2011-01-05 23:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110105234041.GA11813@Krystal \
--to=mathieu.desnoyers@efficios.com \
--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