From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Policy switching and XNOTHER maintenance
Date: Sun, 11 Sep 2011 16:29:32 +0200 [thread overview]
Message-ID: <4E6CC5CC.5020204@domain.hid> (raw)
In-Reply-To: <4E6CC49C.1020403@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
On 2011-09-11 16:24, Gilles Chanteperdrix wrote:
> On 09/11/2011 12:50 PM, Jan Kiszka wrote:
>> 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.
>
> Doing this while holding a mutex looks invalid.
Looking at POSIX e.g., is there anything in the spec that makes this
invalid? If the kernel preserves or established proper priority
boosting, I do not see what could break in principle.
It is nothing I would design into some app, but we should somehow handle
it (doc update or code adjustments).
> If we do not do it, the current code is valid.
Except for its dependency on XNOTHER which is not updated on RT->NORMAL
transitions.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-09-11 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 10:50 [Xenomai-core] Policy switching and XNOTHER maintenance Jan Kiszka
2011-09-11 11:49 ` Jan Kiszka
2011-09-11 14:24 ` Gilles Chanteperdrix
2011-09-11 14:29 ` Jan Kiszka [this message]
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=4E6CC5CC.5020204@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.