From: Jan Kiszka <jan.kiszka@domain.hid>
To: Johan Borkhuis <j.borkhuis@domain.hid>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] Latency calculation and test
Date: Mon, 07 May 2007 15:52:20 +0200 [thread overview]
Message-ID: <463F2F14.1000205@domain.hid> (raw)
In-Reply-To: <463F1D99.5090208@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 3496 bytes --]
Johan Borkhuis wrote:
-snip-
> :| # func -1916 0.512 xntimer_do_tick_aperiodic+0x14 [xeno_nucleus] (xnpod_announce_tick+0x48 [xeno_nucleus])
> :| # func -1916 0.463 xnthread_periodic_handler+0x14 [xeno_nucleus] (xntimer_do_tick_aperiodic+0x2c0 [xeno_nucleus])
> :| # func -1915 0.609 xnpod_resume_thread+0x14 [xeno_nucleus] (xnthread_periodic_handler+0x5c [xeno_nucleus])
> :| # [ 1160] -<?>- 79 -1915 0.878 xnpod_resume_thread+0x78 [xeno_nucleus] (xnthread_periodic_handler+0x5c [xeno_nucleus])
> :| # func -1914 0.365 xnpod_schedule+0x14 [xeno_nucleus] (xnintr_irq_handler+0x1fc [xeno_nucleus])
> :| # [ 0] swapper -1 -1913+ 1.829 xnpod_schedule+0xb8 [xeno_nucleus] (xnintr_irq_handler+0x1fc [xeno_nucleus])
> :| # [ 1160] -<?>- 79 -1912 0.829 xnpod_schedule+0x420 [xeno_nucleus] (xnpod_suspend_thread+0x20c [xeno_nucleus])
> :| # func -1911 0.390 xntimer_get_raw_clock_aperiodic+0x14 [xeno_nucleus] (xnpod_wait_thread_period+0xd0 [xeno_nucleus])
> :| # func -1910 0.317 __ipipe_restore_pipeline_head+0x14 (xnpod_wait_thread_period+0x130 [xeno_nucleus])
> :| + end 0x80000000 -1910+ 1.878 __ipipe_restore_pipeline_head+0xd4 (xnpod_wait_thread_period+0x130 [xeno_nucleus])
> :| + 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 -1856 0.487 __ipipe_dispatch_event+0x14 (do_page_fault+0x188)
> :| + begin 0x80000001 -1855 0.926 __ipipe_dispatch_event+0x27c (do_page_fault+0x188)
> :| + end 0x80000001 -1854 0.585 __ipipe_dispatch_event+0x1a4 (do_page_fault+0x188)
> : + func -1854 0.975 exception_event+0x14 (__ipipe_dispatch_event+0x1bc)
> : + func -1853 0.609 xnarch_trap_fault+0x14 [xeno_nucleus] (exception_event+0x88)
> : + func -1852 0.902 xnpod_trap_fault+0x14 [xeno_nucleus] (xnarch_trap_fault+0x38 [xeno_nucleus])
> : + func -1851 0.878 xnpod_fault_handler+0x14 [xeno_nucleus] (xnpod_trap_fault+0x68 [xeno_nucleus])
> : + func -1851 0.536 xnshadow_relax+0x14 [xeno_nucleus] (xnpod_fault_handler+0x98 [xeno_nucleus])
> :| + begin 0x80000001 -1850+ 1.073 xnshadow_relax+0x15c [xeno_nucleus] (xnpod_fault_handler+0x98 [xeno_nucleus])
> :| # func -1849+ 1.292 schedule_linux_call+0x14 [xeno_nucleus] (xnshadow_relax+0x7c [xeno_nucleus])
> :| # func -1848 1.000 rthal_apc_schedule+0x14 (schedule_linux_call+0xc8 [xeno_nucleus])
> :| # func -1847+ 1.609 __ipipe_schedule_irq+0x14 (rthal_apc_schedule+0x10c)
> :| # 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).
/me has to leave, other may jump in.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2007-05-07 13:52 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 [this message]
2007-05-08 6:57 ` Johan Borkhuis
2007-05-09 7:17 ` Jan Kiszka
2007-05-09 7:49 ` Philippe Gerum
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=463F2F14.1000205@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-help@domain.hid \
--cc=j.borkhuis@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.