All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Haberler <mail17@mah.priv.at>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] kernel equivalent of SIGXCPU
Date: Wed, 22 May 2013 13:47:26 +0200	[thread overview]
Message-ID: <519CB04E.902@xenomai.org> (raw)
In-Reply-To: <519CAB81.40403@xenomai.org>

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.


      reply	other threads:[~2013-05-22 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 10:01 [Xenomai] kernel equivalent of SIGXCPU Michael Haberler
2013-05-22 11:26 ` Gilles Chanteperdrix
2013-05-22 11:47   ` Gilles Chanteperdrix [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=519CB04E.902@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=mail17@mah.priv.at \
    --cc=xenomai@xenomai.org \
    /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.