All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] SCHED_RR
Date: Fri, 05 Dec 2008 16:07:34 +0100	[thread overview]
Message-ID: <493943B6.2040500@domain.hid> (raw)

Hi Gilles,

here is a trivial test case on my desk that points to SCHED_RR issues of
the POSIX skin: simple pthread_create with an attribute block that has
SCHED_RR set, but neither SCHED_RR nor the priority reach the new thread.

The way the scheduling policy and parameters get to that user space
thread leads via __real_pthread_setschedparam after
__pse51_thread_create. This triggers do_setsched_event in shadow.c. But
here we filter out all policies except for SCHED_FIFO. So neither the
priority nor the required XNRRB flag make it to the target therefore.

Even worse, we are running aperiodic timer mode, so this would not have
worked anyway due to the scheduler limitations. Fortunately, it turned
out that the customer is fine with SCHED_FIFO as well, but the broken
priorities and/or lacking error codes on creation are annoying + the
fact that it likely wouldn't work even with periodic timer mode.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 26
Corporate Competence Center Embedded Linux


             reply	other threads:[~2008-12-05 15:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 15:07 Jan Kiszka [this message]
2008-12-05 15:20 ` [Xenomai-core] SCHED_RR Gilles Chanteperdrix
2008-12-05 16:41   ` Jan Kiszka
2008-12-05 16:50     ` Gilles Chanteperdrix
2008-12-05 16:53     ` Gilles Chanteperdrix
2008-12-05 17:41       ` Jan Kiszka
2008-12-05 18:06         ` Gilles Chanteperdrix
2008-12-06 10:32           ` Jan Kiszka
2008-12-06 17:27             ` 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=493943B6.2040500@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.