From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan-Erik Lange <jan0385@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Questio about the Xenomai Scheduler
Date: Mon, 09 Jan 2012 13:16:47 +0100 [thread overview]
Message-ID: <4F0ADAAF.70504@domain.hid> (raw)
In-Reply-To: <BLU166-W50364F5FF2956D7D3F6F78C49B0@domain.hid>
On 01/08/2012 01:06 PM, Jan-Erik Lange wrote:
>
> Is it perhaps this way?:
>
> When the RT-Task migrated into the secondary domain, it is scheduled
> by the Linux-Scheduler:
>
> -> It inherits the RT-priority from her life in the primary domain
> and is timely priviliged compared to other tasks scheduled by the
> linux scheduler, which have a lower priority.
No, a linux task with a higher priority than the RT task running in
secondary mode may preempt the RT task running in secondary mode.
> -> But it can always be
> preempted by an RT-Task, that runs in the primary domain and that is
> scheduled by the Xenomai Scheduler, because this scheduler can
> preempt all standard linux kernel activities.
Yes if root priority inheritance is disabled, not if it is enabled (the
default).
> -> Still it is
> protected from preempting by an Linux interrupt handler, because the
> I-Pipe is block the interrupts.
No, this used to be true a long time ago, but is no longer the case.
You have to consider that an RT task running in secondary mode is an
ordinary linux task. Only tasks remaining in primary mode are deterministic.
--
Gilles.
prev parent reply other threads:[~2012-01-09 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 10:43 [Xenomai-core] Questio about the Xenomai Scheduler Jan-Erik Lange
2012-01-08 12:06 ` Jan-Erik Lange
2012-01-09 12:16 ` 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=4F0ADAAF.70504@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan0385@domain.hid \
--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.