On 05/22/2013 01:26 PM, Gilles Chanteperdrix wrote:
> On 05/22/2013 12:01 PM, Michael Haberler wrote:
>
>> I'm trying to trap scheduling violations through an exception handler
>
>
> How do you define "scheduling violations" ?
>
>>
>> in user RT it's straightforward - use the SIGXCPU handler
>
>
> No, SIGXCPU detect involuntary mode switches to secondary mode, if you
> have the XNWARNSW bit set, it traps Linux system calls made by a thread
> running in secondary mode.
>
>>
>> is rthal_trap_catch() the way to go?
>
>
> rthal_trap_catch, allows to trap machine exceptions.
>
>>
>> or is it just evaluating the rt_task_wait_period() returns ?
>
>
> rt_task_wait_period returns an error when an overrun happens, that is
> when the timer ticks twice without the periodic thread having called
> rt_task_wait_period.
Sorry, when the thread finally wakes up more than one period after its
expected wake up time. So, when the timer ticks twice without the
periodic thread having been scheduled out of rt_taskw_wait_period.
--
Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
