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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
