From: Karim Yaghmour <karim@opersys.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: LTT 0.9.6pre1: Lockless logging, ARM, MIPS, etc.
Date: Thu, 19 Sep 2002 16:10:22 -0400 [thread overview]
Message-ID: <3D8A2F2E.F8E935D2@opersys.com> (raw)
A new development version of LTT, 0.9.6pre1, is now available.
At this point, LTT supports 6 architectures:
i386, PPC, S/390, ARM, SuperH, and MIPS.
Here's what's in 0.9.6pre1:
- Lockless logging implementation a-la K42 by Tom Zanussi (IBM).
This was added to the 2.5.x patch series only.
- ARM port by Frank Rowand (MontaVista).
- MIPS port update/cleanup by Frank Rowand (MontaVista).
- Autotools update by Andrea Cisternino (ST Micro) and Frank
Rowand (MontaVista)
- Added RTAI install script by Klaas Gadeyne to Examples/ directory.
- Added arch/mips/timer.c instrumentation by Bino Mathew (Wipro).
- Fixes for keeping track of event details by Andreas Heppel (Sysgo).
- Fixes for SMP trace analysis by Frank Rowand (MontaVista).
- Moved max limit of IRQ to 256 for XScale by Frank Rowand (MontaVista).
The lockless logging feature is very important because LTT can now
trace a system without using any spinlocks or IRQ disabling whatsoever.
Though this feature is currently only in the 2.5.35 patch included with
LTT, it will be part of all patches for kernels past 2.5.35. At this
time, preliminary testing of the 2.5.35 patch included in 0.9.6pre1
has shown some minor issues which will result in lockups. These issues
will be addressed in a patch I will soon be releasing for 2.5.36.
This is a development release, so the usual warnings apply.
You will find 0.9.6pre1 here:
http://opersys.com/ftp/pub/LTT/
LTT's web site is here:
http://www.opersys.com/LTT
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
reply other threads:[~2002-09-19 20:01 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=3D8A2F2E.F8E935D2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome