All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
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:21:57 +0100	[thread overview]
Message-ID: <45819645.5020600@domain.hid> (raw)
In-Reply-To: <E1GutB2-0005VT-Vb@domain.hid>

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.

A minimum of 50 us is maybe a little bit pessimistic, probably the
effect of the instrumentation itself. But it is true that it is easy to
get high maximum latencies when running the cache calibrator in the
background.

> 
> 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.


This tracer for arm is great.

-- 
                                                 Gilles Chanteperdrix


  reply	other threads:[~2006-12-14 18:21 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 [this message]
2006-12-14 18:59 ` Jan Kiszka
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=45819645.5020600@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --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.