linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Syed Amer Gilani" <amg@systec.de>
To: Linuxppc-embedded@ozlabs.org
Subject: Measure Interrupt Latency on MPC5200B
Date: Thu, 14 Sep 2006 14:00:21 +0200	[thread overview]
Message-ID: <ac3922a00609140500j79e33fb3lfecbefc151ce3b41@mail.gmail.com> (raw)

We have a MPC5200B(ppc) Board from Phytec, running with a 2.6 Linux
Kernel. For Documentation purposes and testings how patches to the
Kernel affects real time capabilities we want to measure the Interrupt
Latency.
I only found tools for other arches or patches for far to old kernels.
Does somebody know a way for a 2.6 kernel on ppc? I already thought of
generating a signal on an Output of the Board and measure it with a
Oscilloscope but i don't find that method satisfying.

Thank you in advance,
Syed Amer Gilani

             reply	other threads:[~2006-09-14 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 12:00 Syed Amer Gilani [this message]
2006-09-19 12:05 ` Measure Interrupt Latency on MPC5200B Josu Onandia
2006-09-19 12:16   ` Esben Nielsen
2006-09-19 12:44     ` Josu Onandia

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=ac3922a00609140500j79e33fb3lfecbefc151ce3b41@mail.gmail.com \
    --to=amg@systec.de \
    --cc=Linuxppc-embedded@ozlabs.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).