2002-04-24 22:10:10

by Karim Yaghmour

[permalink] [raw]
Subject: [ANNOUNCE] Linux Trace Toolkit 0.9.5


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
[email protected]
Embedded and Real-Time Linux Expert
===================================================


2002-04-25 10:25:15

by Roman Zippel

[permalink] [raw]
Subject: Re: [ANNOUNCE] Linux Trace Toolkit 0.9.5

Hi,

On Wed, 24 Apr 2002, Karim Yaghmour wrote:

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

I'd really like to see it go in, but I think some small problems are left,
mostly formatting. Please read Documentation/CodingStyle.
Please use tabs for indentation and not spaces.
You should consider using more inline functions, instead of lots of "do
{...} while(0)" macros.
Do we really need more usages of uint32_t or uint8_t in the kernel?
Instead of using lots of "#ifdef __arch__" you should move this into
<asm/trace.h>.
Comments are nice, but IMO your code does a bit too much of it, e.g.:

/* Everything is OK */
return 0;

or

/* Unlock the table for reading */
read_unlock(&custom_list_lock);

bye, Roman