From: Philippe Gerum <rpm@xenomai.org>
To: Steven Scholz <steven.scholz@domain.hid>
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] xenomai preempting interrupt handler ?
Date: Thu, 08 Mar 2007 13:22:41 +0100 [thread overview]
Message-ID: <1173356561.17515.26.camel@domain.hid> (raw)
In-Reply-To: <45EFF835.9010305@domain.hid>
On Thu, 2007-03-08 at 12:49 +0100, Steven Scholz wrote:
> Philippe,
>
> >>>> Thus will the duration of the
> >>>> ethernet interrupt handler add the the worst case latency?
> >>> Not from Linux IRQ handlers; you may want to check this using the
> >>> tracer. If hw interrupts are masked there, then it's a blatant bug.
> >> How could I check this using the tracer? Small hint please?
> >
> > http://www.xenomai.org/index.php/I-pipe:Tracer
>
> "Traces can be generated in many ways. One happens automatically when
> CONFIG_IPIPE_TRACE_IRQSOFF is enabled."
>
> What exactly does that mean? That one trace is generated during boot?
>
That means that several sources of trace points exist, one of them being
controlled by the IRQSOFF switch. MCOUNT cause a trace to be emitted
upon each function entry, and so on.
> "Another way is to invoke the testsuite, namely latency or irqbench with the
> option -f to trigger a freeze on each new maximum latency."
>
> What exactly does "trigger a freeze" mean?
>
A snapshot of the current trace log, kept from being overwritten in a
separate memory upon freeze, that you can access
through /proc/ipipe/trace/frozen.
> Steven
>
--
Philippe.
prev parent reply other threads:[~2007-03-08 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 9:29 [Xenomai-core] xenomai preempting interrupt handler ? Steven Scholz
2007-03-08 9:42 ` Philippe Gerum
2007-03-08 10:08 ` Steven Scholz
2007-03-08 10:19 ` Philippe Gerum
2007-03-08 10:20 ` Steven Scholz
2007-03-08 10:28 ` Philippe Gerum
2007-03-08 11:49 ` Steven Scholz
2007-03-08 12:22 ` Philippe Gerum [this message]
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=1173356561.17515.26.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=Xenomai-core@domain.hid \
--cc=steven.scholz@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.