All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Linux Trace Toolkit 0.9.5
Date: Wed, 24 Apr 2002 18:08:28 -0400	[thread overview]
Message-ID: <3CC72CDC.CF80C0C6@opersys.com> (raw)


LTT 0.9.5 has now been released.

A very large number of enhancements have been added since 0.9.4. This
is a summary:
o S/390 port 
o SuperH port 
o MIPS port 
o Cross-platform trace reading capabilities 
o Updated RTAI support 
o User-space events (LibUserTrace) 
o Binary traces accessible through user-space library (LibLTT) 
o Visualizer enhancements 
o Dynamic modification of trace masks 
o Autoconf/autobuild build system integration 

For the full detail of the additions, see the news section of the
project's website.

Since LTT is close to 3 years old, it has become a large body of
software. To facilitate easy understanding of what LTT does and what
it doesn't, I've added a "features" description on the project's
front page: http://www.opersys.com/LTT/index.html#features

The list of events traced LTT had been previously documented in
some of the articles I presented about the tool. In order to
facilitate access, I've added an online version of the events
list: http://www.opersys.com/LTT/trace-points.html

As I said earlier, a 2.5.x patch is available and LTT is ready to
be integrated into the 2.5 series.

LTT's website is: http://www.opersys.com/LTT

Cheers,

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

             reply	other threads:[~2002-04-24 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 22:08 Karim Yaghmour [this message]
2002-04-25 10:25 ` [ANNOUNCE] Linux Trace Toolkit 0.9.5 Roman Zippel
2002-05-02 15:17   ` Karim Yaghmour
2002-05-02 20:23     ` Roman Zippel

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=3CC72CDC.CF80C0C6@opersys.com \
    --to=karim@opersys.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 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.