From: Karim Yaghmour <karym@opersys.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ltrace for ppc
Date: Fri, 16 Feb 2001 18:29:16 -0500 [thread overview]
Message-ID: <3A8DB870.B10DA7A2@opersys.com> (raw)
In-Reply-To: 20010216210927.A9F26DBA2E@atlas.valhalla.net
Iain Sandoe wrote:
>
> > If you're interested in ltrace, you may want to take a look at the
> > Linux trace toolkit (http://www.opersys.com/LTT). It runs fine
> > on PPC too.
>
> I'm *very* interested in any toolkit that can provide point-to-point
> _timing_ of system calls, IRQ handling, system usage. latency etc. etc. (a
> la TIMEPEGS or Andrew Morton's amlat on x86).
LTT will definitely give all this and more. It will give you IRQ timings
precise down to the microsecond, same with system calls and any latency.
The measurements it gives are exact, not sampled. Everything you get
corresponds exactly to what happened on your hardware down to the microsecond.
It runs fine on my PowerBook. Give a try and let me know what you think.
>
> what do we have (existing) on PPC?
>
> I did an IRQ latency thing on 2.2.x and Cort has proposed using RTlinux to
> make IRQ measurements (well, I think he's done it, actually)... that will
> give headlines - but not tell us which drivers/functions are the rouges.
LTT will give you the breakdown of how Linux reacts to each IRQ and it is
extendable. Therefore, if you'd like to insert additional trace points in a
driver or another or even an uninstrumented part of the kernel, you'll be able
to create new trace events and see them as part of the trace.
> I was considering doing a port of Andrew Morton's stuff - but got stuck when
> I tried to run with HZ=1024 - it trashed adb... and I haven't got back to it
> yet.
About Andrew Morton's stuff, any pointers?
Best regards,
Karim
===================================================
Karim Yaghmour
karym@opersys.com
Operating System Consultant
(Linux kernel, real-time and distributed systems)
===================================================
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-16 23:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 21:10 ltrace for ppc Iain Sandoe
2001-02-16 22:47 ` Tony Mantler
2001-02-17 12:18 ` Anton Blanchard
2001-02-17 21:11 ` Thomas Graichen
2001-02-16 23:29 ` Karim Yaghmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-17 0:07 Iain Sandoe
2001-02-17 0:22 ` Karim Yaghmour
2001-02-16 23:45 Iain Sandoe
2001-02-16 23:16 Iain Sandoe
2001-02-13 21:10 Anton Blanchard
2001-02-15 17:48 ` Daniel Jacobowitz
2001-02-16 20:58 ` 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=3A8DB870.B10DA7A2@opersys.com \
--to=karym@opersys.com \
--cc=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).