All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <kiszka@domain.hid>
To: ROSSIER Daniel <Daniel.Rossier@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Latencies for the Freescale i.MX21/CSB535FS
Date: Thu, 27 Apr 2006 14:02:00 +0200	[thread overview]
Message-ID: <4450B2B8.1060800@domain.hid> (raw)
In-Reply-To: <FDBBB5CC70676540B3EF7CFE83FD94E0210DD6@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

ROSSIER Daniel wrote:
>>
>> I'd say that the most efficient way to reduce those latencies would
>> require to first identify the source of the 40+ us spot observed with
>> the -t2 form on an idle system. For that, I'm convinced that porting the
>> I-pipe tracer to ARM would be the best option, since this tool would be
>> of great help there.
>>
> Thanks for the hint; we will spend some time on the tracer in the coming days. We keep you informed.
> 

Cool, tracing also for ARM!

>> This port basically requires 1) to code the mcount() routine supporting
>> gcc's -pg option, 2) to solve early boot issues so that mcount() does
>> not attempt to trace anything while the memory environment has not been
>> fully set up. The rest is pretty generic.
>>

Regarding a mcount() implementation and other details, the original
tracer effort by Ingo Molnar may give useful hints (at least it did for me):

http://people.redhat.com/mingo/latency-tracing-patches/

I remember the ARM part not being that simple as x86. I think this was
also due to lacking stack unwinding support on that arch.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2006-04-27 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 11:50 [Xenomai-core] Latencies for the Freescale i.MX21/CSB535FS ROSSIER Daniel
2006-04-27 12:02 ` Jan Kiszka [this message]
2006-04-27 12:13   ` Philippe Gerum
  -- strict thread matches above, loose matches on Subject: below --
2006-04-26  8:08 ROSSIER Daniel
2006-04-26  8:40 ` Philippe Gerum

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=4450B2B8.1060800@domain.hid \
    --to=kiszka@domain.hid \
    --cc=Daniel.Rossier@domain.hid \
    --cc=xenomai@xenomai.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 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.