From: Ingo Molnar <mingo@elte.hu>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: Are ALL_TASKS_PI on in 2.6.16-rt7?
Date: Sun, 26 Mar 2006 23:35:52 +0200 [thread overview]
Message-ID: <20060326213552.GA1963@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0603262231110.8060-100000@lifa03.phys.au.dk>
* Esben Nielsen <simlo@phys.au.dk> wrote:
> On Sun, 26 Mar 2006, Ingo Molnar wrote:
>
> >
> > * Esben Nielsen <simlo@phys.au.dk> wrote:
> >
> > > It just looks like also normal, non-rt tasks are boosting.
> >
> > correct. We'd like to make sure the PI code is correct - and for
> > PI-futex it makes sense anyway.
> >
>
> It wont work 100% when a task is boosted to a normal, non-rt prio well
> since at scheduler_tick()
> p->prio = effective_prio(p);
> can be executed overwriting the boost.
yeah - but that's relatively rare, upon expiration of the timeslice.
The following would probably solve it: scheduler_tick() could take the
pi_lock (before taking the rq lock), update normal_prio, and then call
into rt_mutex_getprio() [just like setscheduler does] to set the
priority.
Ingo
prev parent reply other threads:[~2006-03-26 21:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:07 Are ALL_TASKS_PI on in 2.6.16-rt7? Esben Nielsen
2006-03-26 21:23 ` 2.6.16-rt7 and deadlock detection Esben Nielsen
2006-03-26 22:04 ` Esben Nielsen
2006-03-26 22:04 ` Ingo Molnar
2006-03-26 23:35 ` 2.6.16-rt10 Ingo Molnar
2006-03-28 9:43 ` 2.6.16-rt10 Simon Derr
2006-03-28 20:49 ` 2.6.16-rt10 Ingo Molnar
2006-03-29 7:55 ` 2.6.16-rt10 Simon Derr
2006-04-04 11:57 ` 2.6.16-rt10 Simon Derr
2006-04-04 12:00 ` 2.6.16-rt10 Ingo Molnar
2006-04-04 15:59 ` 2.6.16-rt10 Simon Derr
2006-04-04 19:27 ` 2.6.16-rt10 Steven Rostedt
2006-03-26 21:27 ` Are ALL_TASKS_PI on in 2.6.16-rt7? Ingo Molnar
2006-03-26 21:33 ` Esben Nielsen
2006-03-26 21:35 ` Ingo Molnar [this message]
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=20060326213552.GA1963@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=simlo@phys.au.dk \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox