All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: Takeharu Kato <tk1219@alles.or.jp>
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 12:19:51 -0400	[thread overview]
Message-ID: <3DB034A7.D7E9BA78@opersys.com> (raw)
In-Reply-To: 3DB03026.63AF250F@alles.or.jp


Takeharu Kato wrote:
> Karim Yaghmour wrote:
> >
> > A new development version of LTT is now available, 0.9.6pre2.
> > Here's what's new:
> > - Per-CPU buffering
> > - TSC timestamping
> > - Use of syscall interface instead of char dev abstraction
> >
> As long as I think, 0.9.6pre2 has called CHAR DEV in LibUserTrace.
> Should I apply the patch which you send before?

0.9.6pre2 is a development version, it's expected to have rough
spots. If you need a stable version use 0.9.5a. That said, yes
LibUserTrace hasn't been modified yet for the syscall interface,
but this is really a minor issue which will be fixed.

Karim

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

  reply	other threads:[~2002-10-18 16:09 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 [this message]
2002-10-18 16:20     ` Takeharu Kato
2002-10-18 18:32 ` Frank Rowand
2002-10-18 19:00   ` Karim Yaghmour

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=3DB034A7.D7E9BA78@opersys.com \
    --to=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.org \
    --cc=tk1219@alles.or.jp \
    /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.