All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Simon <Daniel.Simon@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Posix skin illegal seek on sem_wait
Date: Tue, 25 Apr 2006 16:54:23 +0200	[thread overview]
Message-ID: <20060425165423.7b7d231b@domain.hid> (raw)
In-Reply-To: <17486.10146.597736.78655@domain.hid>

On Tue, 25 Apr 2006 15:44:02 +0200
Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:

> The term "Xenomai thread" comes from the document "Life with Adeos":

The shadowing process is not clear in this paper, e.g. bottom of page 6:

<<Xenomai allows to run real-time threads either strictly in kernel
space, or within the address space of a Linux process. In the rest of
this article, we will refer to the latter as the Xenomai threads, not
to be confused with regular Linux tasks (even when they belong to the
SCHED_FIFO class).>> 

I guess that "regular Linux tasks unknown to Xenomai, and which
only happen to belong to the SCHED_FIFO class" are those compiled and
linked against the regular pthread library?

Anyway, my threads are created with the SCHED_FIFO flag; may be there
is a conflict with main() which, as I understand, can be only a regular
thread?

>signals sent by the timer_* services will
>cause migration of the target thread to secondary mode

I notice that timer_settime(...) also returns an error (perror
says "Operation not permitted" while errno is set to 29 "illegal
seek", as for the sem_wait)

>signals [...] cause migration of the target thread to secondary mode

is it only a "not yet implemented" feature or is it a basic
conflict between signals and hard real-time?

	Thanks

		Daniel 




  reply	other threads:[~2006-04-25 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 11:43 [Xenomai-help] Posix skin illegal seek on sem_wait Daniel Simon
2006-04-25 13:44 ` Gilles Chanteperdrix
2006-04-25 14:54   ` Daniel Simon [this message]
2006-04-25 15:12     ` Gilles Chanteperdrix
2006-04-25 16:04     ` Gilles Chanteperdrix

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=20060425165423.7b7d231b@domain.hid \
    --to=daniel.simon@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.