From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] Latency calculation and test
Date: Wed, 09 May 2007 09:49:11 +0200 [thread overview]
Message-ID: <1178696951.5004.2.camel@domain.hid> (raw)
In-Reply-To: <464175A7.6060504@domain.hid>
On Wed, 2007-05-09 at 09:17 +0200, Jan Kiszka wrote:
> Johan Borkhuis wrote:
> > Jan,
> >
> > Jan Kiszka wrote:
> >> Johan Borkhuis wrote:
> >> -snip-
> >>
> >>> :| + begin 0x80000001 -1908 0.414 __ipipe_dispatch_event+0x1e4
> >>> (__ipipe_syscall_root+0x64)
> >>> :| + end 0x80000001 -1908! 52.121 __ipipe_dispatch_event+0x204
> >>> (__ipipe_syscall_root+0x64)
> >>> : + func -1857+ 1.170 do_page_fault+0x14
> >>> (handle_page_fault+0xc)
> >>>
> >> This one is interesting: page fault over the RT-thread that belongs to
> >> PID 1160 (prio 79).
> >>
> >>> :| # func -1845+ 1.585 rpi_push+0x14 [xeno_nucleus]
> >>> (xnshadow_relax+0x84 [xeno_nucleus])
> >>> :| # func -1844 0.463 xnpod_schedule_runnable+0x14
> >>> [xeno_nucleus] (rpi_push+0x84 [xeno_nucleus])
> >>> :| # [ 0] swapper 79 -1843+ 1.658 xnpod_schedule_runnable+0x54
> >>> [xeno_nucleus] (rpi_push+0x84 [xeno_nucleus])
> >>>
> >> And now we are running the Linux kernel at xeno-prio 79 (due to
> >> prio-coupling).
> >>
> > Thank you for pointing these out. This made me change 2 things in the
> > configuration:
> > - Disabling swap. This should not make any difference as I don't have
> > any swapspace, but the page_fault triggered me to have a look at that
> > setting.
> > - Enabling "Disable priority coupling". I missed the Disable part here,
> > so it was still enabled during this run.
>
> Don't get me wrong: I was not saying the prio-coupling it the root of
> the problem here, it's just an amplifier. The (or at least one) root is
> that your RT task still causes page faults. That needs to be fixed!
>
Additionally, prio coupling should not be applied when transitioning to
secondary mode is caused by special operations, like handling a fault or
exiting. I'm going to have a look at this.
--
Philippe.
next prev parent reply other threads:[~2007-05-09 7:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 12:35 [Xenomai-help] Latency calculation and test Johan Borkhuis
2007-05-03 13:29 ` Philippe Gerum
2007-05-03 14:07 ` Gilles Chanteperdrix
2007-05-04 7:58 ` Johan Borkhuis
2007-05-04 9:17 ` Gilles Chanteperdrix
2007-05-04 12:32 ` Philippe Gerum
2007-05-04 12:43 ` Jan Kiszka
2007-05-07 6:51 ` Johan Borkhuis
2007-05-07 8:29 ` Johan Borkhuis
2007-05-07 8:58 ` Jan Kiszka
2007-05-07 11:58 ` Johan Borkhuis
2007-05-07 12:11 ` Jan Kiszka
2007-05-07 12:37 ` Johan Borkhuis
2007-05-07 13:52 ` Jan Kiszka
2007-05-08 6:57 ` Johan Borkhuis
2007-05-09 7:17 ` Jan Kiszka
2007-05-09 7:49 ` Philippe Gerum [this message]
2007-05-07 12:30 ` Gilles Chanteperdrix
2007-05-07 13:21 ` Jan Kiszka
2007-05-03 13:42 ` Daniel Schnell
2007-05-03 14:54 ` Philippe Gerum
2007-05-03 15:07 ` Gilles Chanteperdrix
2007-05-03 15:43 ` Daniel Schnell
2007-05-03 18:42 ` Gilles Chanteperdrix
2007-05-03 18:47 ` Jan Kiszka
2007-05-04 6:51 ` Daniel Schnell
2007-05-03 16:11 ` Philippe Gerum
2007-05-03 16:44 ` Gilles Chanteperdrix
2007-05-03 17:17 ` Philippe Gerum
2007-05-03 17:26 ` Jan Kiszka
2007-05-04 12:46 ` Bill Gatliff
2007-05-04 8:04 ` Johan Borkhuis
2007-05-03 14:38 ` Gilles Chanteperdrix
2007-05-03 19:23 ` Gilles Chanteperdrix
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=1178696951.5004.2.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=Xenomai-help@domain.hid \
--cc=jan.kiszka@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.