From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] newbie question
Date: Mon, 06 Aug 2007 21:27:13 +0200 [thread overview]
Message-ID: <1186428434.5963.12.camel@domain.hid> (raw)
In-Reply-To: <18103.24835.247952.219162@domain.hid>
On Mon, 2007-08-06 at 19:57 +0200, Gilles Chanteperdrix wrote:
> rolfetas bambolas wrote:
> > Hi to all,
> > I'm trying to understand how Xenomai handles priorities, and found a paper
> > called "Life with Adeos" from 2005 which explains that tasks in secondary
> > mode force the linux kernel to inherit the RT-Tasks priority.
> > I also read that User-Space RT Tasks migrate to secondary mode when they
> > make a system call to the linux-kernel, and migrate back when they use some
> > Xenomai API.
> >
> > Does this mean, that the Linux-Kernel will keep the inherited priority until
> > the RT-Task calls again Xenomai?? what happens is a RT-Task doesn't call
> > Xenomai for a while??
> > I hope you understand what I mean,
> > Thank you,
>
> What you are referring to is the priority coupling between Xenomai and
> Linux schedulers, and can be disabled in Xenomai configuration.
>
> The linux kernel will keep the inherited priority until the RT-task
> calls xenomai again, or until it is suspended by Linux scheduler. If the
> RT-task does not call xenomai for a while (and is not suspended by Linux
> scheduler), then, well, it is an RT-task after all and should be able to
> run until it reaches a suspension point or wakes up another RT-task.
>
> Note however that during this time, Linux interruptions will be allowed
> to preempt the RT-task.
>
(unless the interrupt shield is in effect).
--
Philippe.
next prev parent reply other threads:[~2007-08-06 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 15:15 [Xenomai-help] newbie question rolfetas bambolas
2007-08-06 17:57 ` Gilles Chanteperdrix
2007-08-06 18:23 ` juanba romance
2007-08-06 19:29 ` Gilles Chanteperdrix
[not found] ` <e39c9190708061427y2d5ceed2td804b0990b88f282@domain.hid>
2007-08-06 21:37 ` Gilles Chanteperdrix
2007-08-06 19:27 ` Philippe Gerum [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 10:46 Daniele Lugli
2006-03-16 11:18 ` Philippe Gerum
2006-03-16 11:38 ` Jan Kiszka
2006-03-16 12:33 ` Philippe Gerum
2005-10-17 18:44 [Xenomai-help] compiling xenomai on x86_64 Jan Kiszka
2005-10-17 18:57 ` Heikki Lindholm
2005-10-17 19:16 ` Jan Kiszka
2005-10-17 19:59 ` Heikki Lindholm
2005-10-17 20:04 ` Philippe Gerum
2005-10-17 20:10 ` Jan Kiszka
2005-10-17 20:17 ` Philippe Gerum
2005-10-17 20:26 ` Philippe Gerum
2005-10-17 21:37 ` Jan Kiszka
2005-10-18 8:07 ` Jan Kiszka
2005-10-18 17:49 ` Gilles Chanteperdrix
2005-10-18 18:29 ` Jan Kiszka
2005-10-18 19:20 ` Gilles Chanteperdrix
2005-10-18 19:24 ` Jan Kiszka
2005-10-18 19:34 ` Gilles Chanteperdrix
2005-10-18 19:43 ` Jan Kiszka
2005-10-19 8:37 ` Jan Kiszka
2005-10-19 17:15 ` [Xenomai-help] newbie question Ignacio García Pérez
2005-10-19 17:34 ` Jan Kiszka
2005-10-19 17:44 ` Philippe Gerum
2005-10-19 18:16 ` Gilles Chanteperdrix
2005-10-19 18:31 ` Jan Kiszka
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=1186428434.5963.12.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=Xenomai-help@domain.hid \
--cc=gilles.chanteperdrix@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.