From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [PATCH v2 1/4] POSIX: Fix SCHED_RR thread creation
Date: Tue, 17 Feb 2009 18:17:28 +0000 [thread overview]
Message-ID: <499AFF38.5030509@domain.hid> (raw)
In-Reply-To: <499AFA8D.3080302@domain.hid>
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Jan Kiszka wrote:
>>>>> Gilles Chanteperdrix wrote:
>>>>>> Jan Kiszka wrote:
>>>>>>> @@ -192,6 +192,9 @@ static void *__pthread_trampoline(void *arg)
>>>>>>>
>>>>>>> param.sched_priority = iargs->prio;
>>>>>>> policy = iargs->policy;
>>>>>>> + if (policy == SCHED_RR)
>>>>>>> + /* Restrict round-robin scheduling to the Xenomai domain. */
>>>>>>> + policy = SCHED_FIFO;
>>>>>> Should not there be the same thing in __wrap_pthread_setschedparam ?
>>>>> Yes, and setschedparam_ex, here we go:
>>>> Actually, I am wondering if we can not get rid of these calls to
>>>> __real_pthread_setschedparam, now that propagating kernel-space priority
>>>> to user-space is done by a signal ?
>>> Not with the existing code, as that only forwards prio changes, but no
>>> policy changes.
>> If we map SCHED_RR to SCHED_FIFO, are there any policy changes?
>
> Yes, the initial one. Keep in mind that not all pthread implementations
> may respect the pthread_attr or have problems assigning SCHED_FIFO to
> threads of non-root users.
Ok. What about calling xnshadow_renice in xnshadow_map ?
--
Gilles.
next prev parent reply other threads:[~2009-02-17 18:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 17:04 [Xenomai-core] [PATCH v2 0/4] Various fixes and cleanups Jan Kiszka
2009-02-17 17:04 ` [Xenomai-core] [PATCH v2 2/4] Mark libs nodlopen on initial-exec TLS Jan Kiszka
2009-02-17 17:04 ` [Xenomai-core] [PATCH v2 3/4] Add --enable-dlopen-skins configure switch Jan Kiszka
2009-02-17 17:04 ` [Xenomai-core] [PATCH v2 4/4] POSIX: Do not auto-shadow main with dlopen enabled Jan Kiszka
2009-02-17 17:04 ` [Xenomai-core] [PATCH v2 1/4] POSIX: Fix SCHED_RR thread creation Jan Kiszka
2009-02-17 17:15 ` Gilles Chanteperdrix
2009-02-17 17:28 ` Jan Kiszka
2009-02-17 17:37 ` Gilles Chanteperdrix
2009-02-17 17:47 ` Jan Kiszka
2009-02-17 17:50 ` Gilles Chanteperdrix
2009-02-17 17:57 ` Jan Kiszka
2009-02-17 18:17 ` Gilles Chanteperdrix [this message]
2009-02-17 18:19 ` Jan Kiszka
2009-02-17 18:21 ` Gilles Chanteperdrix
2009-02-17 18:41 ` Jan Kiszka
2009-02-17 23:48 ` Jan Kiszka
2009-02-18 7:51 ` Jan Kiszka
2009-02-25 10:04 ` [Xenomai-core] [PATCH v2 0/4] Various fixes and cleanups Jan Kiszka
2009-02-25 11:19 ` 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=499AFF38.5030509@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=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.