From: Karim Yaghmour <karym@opersys.com>
To: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
Cc: linux-kernel@vger.kernel.org, Robert Love <rml@tech9.net>
Subject: Re: [PATCH] latency-profiling
Date: Thu, 20 Sep 2001 16:17:25 -0400 [thread overview]
Message-ID: <3BAA4ED5.EDEF3047@opersys.com> (raw)
In-Reply-To: <200109200609.f8K69uQ26778@mailc.telia.com>
Roger Larsson wrote:
> This patch works a little different from Robert Loves.
> Since it samples the execution location at ticks.
> It is possible to instrument an ordinary kernel too...
You could also try the Linux Trace Toolkit which would provide
you with much more accurate results and exact times instead of
samples. LTT is here: http://www.opersys.com/LTT
Cheers,
Karim
===================================================
Karim Yaghmour
karym@opersys.com
Embedded and Real-Time Linux Expert
===================================================
prev parent reply other threads:[~2001-09-21 2:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 6:05 [PATCH] latency-profiling Roger Larsson
2001-09-20 19:55 ` george anzinger
2001-09-20 20:31 ` Roger Larsson
2001-09-20 20:17 ` 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=3BAA4ED5.EDEF3047@opersys.com \
--to=karym@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=roger.larsson@skelleftea.mail.telia.com \
/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