From: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Pending patches
Date: Thu, 15 Jan 2009 22:46:21 +0100 [thread overview]
Message-ID: <496FAEAD.3060604@domain.hid> (raw)
In-Reply-To: <496F457A.5030000@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2315 bytes --]
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Jan Kiszka wrote:
>>>>> commit 028d4766a38b6937d9a2c02a20022e3ee5b67b55
>>>>> Author: Jan Kiszka <jan.kiszka@domain.hid>
>>>>> Date: Thu Jan 15 11:10:24 2009 +0100
>>>>>
>>>>> POSIX: Fix initialization of SCHED_RR threads
>>>>>
>>>>> Passing SCHED_RR as policy to pthread_create has currently not the
>>>>> desired effect. The kernel part expects that user space adjusts the
>>>>> policy and prio via __pse51_thread_setschedparam after setting up the
>>>>> shadow. And this is what the patch does by calling the wrapped
>>>>> pthread_setschedparam instead of the real one.
>>>>>
>>>>> Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
>>>>>
>>>>> src/skins/posix/thread.c | 2 +-
>>>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>>>
>>>>> commit 71666ce04ef216d281fe86ee82a5560c2b57c6dd
>>>>> Author: Jan Kiszka <jan.kiszka@domain.hid>
>>>>> Date: Thu Jan 15 11:10:24 2009 +0100
>>>>>
>>>>> Handle priority changes of SCHED_RR tasks
>>>>>
>>>>> If shadowed Linux tasks with SCHED_RR policy change their priority,
>>>>> do_setsched_event currenty ignores this. Extend the condition to catch
>>>>> this case as well.
>>>>>
>>>>> Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
>>>>>
>>>>> ksrc/nucleus/shadow.c | 2 +-
>>>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>>>
>>>> Nack these two ones too. Philippe implemented a SCHED_RR working over
>>>> aperiodic mode. I think the POSIX skin needs fixing, but not that way.
>>> Then please suggest a better fix.
>> I thought I did: simply pass the SCHED_RR option to kernel-space and
>> handle it there, but replace it with SCHED_FIFO for anything in
>> user-space. I plan to do it, but trunk is not my current priority.
>
> This is also a stable bug (so the final version should also be
> backported). However, I will check your proposal.
Extending the __pse51_thread_create syscall to also take the sched
policy is likely no option to fix 2.4.x -- ABI breakage...
Suggestion: Apply my original fix to stable but go the enhanced
__pse51_thread_create path for trunk (I'm working on the latter ATM).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-01-15 21:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 10:19 [Xenomai-core] Pending patches Jan Kiszka
2009-01-15 10:30 ` Gilles Chanteperdrix
2009-01-15 11:00 ` Gilles Chanteperdrix
2009-01-15 11:31 ` Jan Kiszka
2009-01-15 13:02 ` Gilles Chanteperdrix
2009-01-15 14:12 ` Jan Kiszka
2009-01-15 11:28 ` Jan Kiszka
2009-01-15 13:09 ` Gilles Chanteperdrix
2009-01-15 14:17 ` Jan Kiszka
2009-01-15 21:46 ` Jan Kiszka [this message]
2009-01-15 10:49 ` Philippe Gerum
2009-01-15 11:24 ` Jan Kiszka
2009-01-15 12:09 ` Philippe Gerum
2009-01-15 13:55 ` Jan Kiszka
2009-01-15 14:16 ` Philippe Gerum
2009-01-19 23:18 ` Philippe Gerum
2009-01-19 23:35 ` Jan Kiszka
2009-01-20 8:49 ` Philippe Gerum
2009-01-20 9:06 ` Jan Kiszka
2009-01-20 9:18 ` Jan Kiszka
2009-01-20 9:22 ` Philippe Gerum
2009-01-27 13:10 ` Jan Kiszka
2009-01-27 13:26 ` Jan Kiszka
2009-01-27 13:28 ` Gilles Chanteperdrix
2009-01-27 13:29 ` Philippe Gerum
2009-01-27 13:40 ` Gilles Chanteperdrix
2009-01-27 13:40 ` Philippe Gerum
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=496FAEAD.3060604@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.