From: Jan Kiszka <jan.kiszka@domain.hid>
To: Sebastian Smolorz <ssm@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Latency trace on ARM
Date: Thu, 14 Dec 2006 19:59:06 +0100 [thread overview]
Message-ID: <45819EFA.2090908@domain.hid> (raw)
In-Reply-To: <E1GutB2-0005VT-Vb@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Sebastian Smolorz wrote:
> Hi,
>
> we all know that the latency test should not be run with a period of 100 us
> because it easily gets locked up. The attached trace illustrates this problem
> in detail. It shows that a timer interrupt needs about 50 us to be processed.
> Furthermore, there is not enough time between two timer interrupts for the
> latency task to get all its work done.
>
> The current I-pipe tracer patch for ARM is available at
> http://opensource.emlix.com/ipipe-s3c24xx/download/ipipe-tracer-arm.patch_v4
>
> Comments welcome.
Something is still broken, given all those "N"s in Delay column. Is
there something like NMI at all on your board?
BTW, two asses the tracer's overhead, you may want to run some
consecutive ipipe_trace_specials and watch the result in the log. Should
be around 1.something per trace point.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-12-14 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 16:11 [Adeos-main] Latency trace on ARM Sebastian Smolorz
2006-12-14 18:21 ` Gilles Chanteperdrix
2006-12-14 18:59 ` Jan Kiszka [this message]
2006-12-15 9:48 ` Sebastian Smolorz
2006-12-15 9:53 ` Jan Kiszka
2006-12-15 14:30 ` Sebastian Smolorz
2006-12-15 14:39 ` Jan Kiszka
2006-12-18 10:52 ` Sebastian Smolorz
2006-12-18 11:55 ` Jan Kiszka
2006-12-18 16:04 ` [Xenomai-core] " Sebastian Smolorz
2006-12-18 20:28 ` Philippe Gerum
2006-12-18 21:52 ` Sebastian Smolorz
2006-12-18 22:04 ` Philippe Gerum
2006-12-19 13:58 ` Sebastian Smolorz
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=45819EFA.2090908@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=ssm@domain.hid \
/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.