From: Karim Yaghmour <karym@opersys.com>
To: linux-kernel@vger.kernel.org, realtime@realtimelinux.org
Subject: [ANNOUNCE] Linux Trace Toolkit version 0.9.4
Date: Tue, 20 Mar 2001 01:58:28 -0500 [thread overview]
Message-ID: <3AB6FF94.D957087B@opersys.com> (raw)
This new release of the Linux Trace Toolkit includes complete
support for Linux and RTAI on both ix86 and PPC. With this out,
work on other architectures is in its way. Anyone wanting
to dig-in is welcomed to do so.
Also, 0.9.4 includes all the additions that were made in the
0.9.4preX series. This includes interfacing with DProbes
using dynamic event creation and usage of rvmalloc and friends
to avoid having to copy large portions of memory from kernel
space to user space.
In order to encourage exchanges and discussions, I've set
up mailing lists for LTT. Please take a look at the "mailing
lists" section of the project's web-site for more detail.
You can find LTT at:
http://www.opersys.com/LTT
Cheers,
Karim Yaghmour
===================================================
Karim Yaghmour
karym@opersys.com
Embedded and Real-Time Linux Expert
===================================================
reply other threads:[~2001-03-20 6:53 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=3AB6FF94.D957087B@opersys.com \
--to=karym@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=realtime@realtimelinux.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