From: Jan Kiszka <jan.kiszka@domain.hid>
To: Paul Ianna <paulianna2002@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] primary mode versus secondary mode
Date: Mon, 21 Aug 2006 22:44:26 +0200 [thread overview]
Message-ID: <44EA1B2A.5010402@domain.hid> (raw)
In-Reply-To: <75975c320608211321u5b2d9e45nfb078e9ed4d8b617@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Paul Ianna wrote:
> Hi All,
>
> I have read (at least some of) the Xenomai docs and am a little
> unclear on the real distinction between primary and secondary mode.
>
> I have seen in the native API that I can receive a signal if a task
> has "migrated to the Linux domain".
>
> Does secondary mode mean that I am no longer a real-time task?
As long as your task is in this mode, Linux can do with it again what it
wants to. This phase ends once you call a Xenomai service that requires
primary mode or you enforce a mode switch (rt_task_set_mode, but for
most applications designs not required).
>
> How do I avoid dropping from primary mode to secondary mode?
Avoid executing Linux system services (file I/O, networking, printf,
etc.) in critical code paths, avoid sending Linux signal to the task.
But if you write a hard real-time application, you are likely doing a
careful review of what your time-critical code finally does anyway ;).
If not (don't tell it anyone...), the SIGXCPU signal raised on mode
switches can guide you finding fishy parts.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2006-08-21 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <75975c320608211235l79dfb17ft54df1018e7f597ff@domain.hid>
2006-08-21 20:21 ` [Xenomai-help] primary mode versus secondary mode Paul Ianna
2006-08-21 20:42 ` Philippe Gerum
2006-08-23 20:00 ` Paul Ianna
2006-08-23 20:17 ` Philippe Gerum
2006-08-21 20:44 ` Jan Kiszka [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=44EA1B2A.5010402@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=paulianna2002@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.