From: Karim Yaghmour <karim@opersys.com>
To: frowand@mvista.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
LTT-Dev <ltt-dev@shafik.org>
Subject: Re: [ltt-dev] [ANNOUNCE] LTT 0.9.6pre2: Per-CPU buffers, TSC timestamps, etc.
Date: Fri, 18 Oct 2002 15:00:48 -0400 [thread overview]
Message-ID: <3DB05A60.5D64425@opersys.com> (raw)
In-Reply-To: 3DB053C4.8458B0D8@mvista.com
Frank Rowand wrote:
> I noticed that the Linux 2.4.19 patch is not carried forward from
> pre1 to pre2. Are you planning to no longer maintain support for
> LTT in the Linux 2.4 line?
The problem is that the kernel patch is highly dependent on the kernel's
own development. The tracing infrastructure has to change as the kernel
changes. Incidently, the user tools also have to change to accomodate
the newer kernels. There's a point where keeping compatibility with
older kernels becomes increasingly difficult and would entail one of
two things:
- Burden the user tools with legacy support.
- Backport all new features to older kernels.
Neither of these is really interesting. Of course, if someone wants to
take the time to backport some of the new features to older kernels
I would gladly publish their patch with the tools. The time it takes
to work out an LTT patch is non-negligeable and I don't have the
bandwidth to maintain multiple kernel patches in parallel. This is
why I'm concentrating on getting LTT to work with the latest and
greatest.
Obviously things will be much simpler once the LTT patch is included
in the kernel.
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
prev parent reply other threads:[~2002-10-18 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 3:50 [ANNOUNCE] LTT 0.9.6pre2: Per-CPU buffers, TSC timestamps, etc Karim Yaghmour
2002-10-18 16:00 ` [ltt-dev] " Takeharu Kato
2002-10-18 16:19 ` Karim Yaghmour
2002-10-18 16:20 ` Takeharu Kato
2002-10-18 18:32 ` Frank Rowand
2002-10-18 19:00 ` Karim Yaghmour [this message]
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=3DB05A60.5D64425@opersys.com \
--to=karim@opersys.com \
--cc=frowand@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.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.