All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Policy switching and XNOTHER maintenance
Date: Sun, 11 Sep 2011 12:50:39 +0200	[thread overview]
Message-ID: <4E6C927F.3070901@domain.hid> (raw)

[-- Attachment #1: Type: text/plain, Size: 771 bytes --]

Hi all,

just looked into the hrescnt issue again, specifically the corner case
of a shadow thread switching from real-time policy to SCHED_OTHER.

Looks like we don't support this at all ATM:

do_setsched_event ignores events that enabled SCHED_OTHER, and the
XNOTHER flag is only set on xnshadow_map, not updated anywhere else.
Fixing this is not straightforward as that flag resides in a state
variable that is owned by the thread (ie. updated non-atomically) while
do_setsched_event can also be called over different contexts.

Or am I missing something?

In the light of this, I would vote for reverting f9bfab3457 ("only
update rescnt for XNOTHER threads") as it only adds conditional branches
to the hot paths without solving the issue.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

             reply	other threads:[~2011-09-11 10:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-11 10:50 Jan Kiszka [this message]
2011-09-11 11:49 ` [Xenomai-core] Policy switching and XNOTHER maintenance Jan Kiszka
2011-09-11 14:24 ` Gilles Chanteperdrix
2011-09-11 14:29   ` Jan Kiszka
2011-09-16 20:13     ` Gilles Chanteperdrix
2011-09-16 20:39       ` Gilles Chanteperdrix
2011-09-18 14:02         ` Philippe Gerum
2011-09-18 14:34           ` Jan Kiszka
2011-09-18 15:10             ` Philippe Gerum
2011-09-18 15:11               ` Jan Kiszka
2011-09-18 15:13                 ` Jan Kiszka
2011-09-18 15:18                   ` Gilles Chanteperdrix
2011-09-18 15:24                     ` Jan Kiszka
2011-09-18 15:47                       ` 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=4E6C927F.3070901@domain.hid \
    --to=jan.kiszka@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.