public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Onkalo Samu <samu.p.onkalo@nokia.com>
To: ext Peter Zijlstra <peterz@infradead.org>
Cc: Yong Zhang <yong.zhang0@gmail.com>,
	mingo@elte.hu,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	tglx <tglx@linutronix.de>
Subject: Re: Bug in scheduler when using rt_mutex
Date: Wed, 19 Jan 2011 15:13:19 +0200	[thread overview]
Message-ID: <1295442799.11678.43.camel@kolo> (raw)
In-Reply-To: <1295441881.11678.41.camel@kolo>

On Wed, 2011-01-19 at 14:58 +0200, Onkalo Samu wrote:
> On Wed, 2011-01-19 at 12:30 +0100, ext Peter Zijlstra wrote:
> > On Wed, 2011-01-19 at 11:38 +0100, Peter Zijlstra wrote:
> > 
> > > Hrm, I think the to bit is not needed with the from thing in place, the
> > > enqueue from _setprio will already have added min_vruntime
> > 
> > 
> > Would lead to something like this:
> > 
> 
> Doesn't work in my case.

When the task is sleeping rt_mutex_setprio
doesn't call check_class_changed since the task is not 
in queue at that moment I think.

> 
> > ---
> > Index: linux-2.6/kernel/sched.c
> > ===================================================================
> > --- linux-2.6.orig/kernel/sched.c
> > +++ linux-2.6/kernel/sched.c
> > @@ -8108,6 +8108,8 @@ EXPORT_SYMBOL(__might_sleep);
> >  #ifdef CONFIG_MAGIC_SYSRQ
> >  static void normalize_task(struct rq *rq, struct task_struct *p)
> >  {
> > +	struct sched_class *prev_class = p->sched_class;
> > +	int old_prio = p->prio;
> >  	int on_rq;
> >  
> >  	on_rq = p->se.on_rq;
> > @@ -8118,6 +8120,8 @@ static void normalize_task(struct rq *rq
> >  		activate_task(rq, p, 0);
> >  		resched_task(rq->curr);
> >  	}
> > +
> > +	check_class_changed(rq, p, prev_class, old_prio, task_current(rq, p));
> >  }
> >  
> >  void normalize_rt_tasks(void)
> > Index: linux-2.6/kernel/sched_fair.c
> > ===================================================================
> > --- linux-2.6.orig/kernel/sched_fair.c
> > +++ linux-2.6/kernel/sched_fair.c
> > @@ -4066,11 +4066,30 @@ static void prio_changed_fair(struct rq
> >  		check_preempt_curr(rq, p, 0);
> >  }
> >  
> > +static void
> > +switched_from_fair(struct rq *rq, struct task_struct *p, int running)
> > +{
> > +	struct sched_entity *se = &p->se;
> > +	struct cfs_rq *cfs_rq = cfs_rq_of(se);
> > +
> > +	/*
> > +	 * Ensure the task's vruntime is normalized, so that when its
> > +	 * switched back to the fair class the enqueue_entity(.flags=0) will
> > +	 * do the right thing.
> > +	 *
> > +	 * If it was on_rq, then the dequeue_entity(.flags=0) will already
> > +	 * have normalized the vruntime, if it was !on_rq, then only when
> > +	 * the task is sleeping will it still have non-normalized vruntime.
> > +	 */
> > +	if (!se->on_rq && p->state != TASK_RUNNING)
> > +		se->vruntime -= cfs_rq->min_vruntime;
> > +}
> > +
> >  /*
> >   * We switched to the sched_fair class.
> >   */
> > -static void switched_to_fair(struct rq *rq, struct task_struct *p,
> > -			     int running)
> > +static void
> > +switched_to_fair(struct rq *rq, struct task_struct *p, int running)
> >  {
> >  	/*
> >  	 * We were most likely switched from sched_rt, so
> > @@ -4163,6 +4182,7 @@ static const struct sched_class fair_sch
> >  	.task_fork		= task_fork_fair,
> >  
> >  	.prio_changed		= prio_changed_fair,
> > +	.switched_from		= switched_from_fair,
> >  	.switched_to		= switched_to_fair,
> >  
> >  	.get_rr_interval	= get_rr_interval_fair,
> > 
> 
> 



  reply	other threads:[~2011-01-19 13:08 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 14:42 Bug in scheduler when using rt_mutex Onkalo Samu
2011-01-17 15:00 ` Peter Zijlstra
2011-01-17 15:15   ` samu.p.onkalo
2011-01-17 15:28     ` Peter Zijlstra
2011-01-17 16:00 ` Peter Zijlstra
2011-01-18  8:23   ` Onkalo Samu
2011-01-18  8:59     ` Yong Zhang
2011-01-18 13:35       ` Peter Zijlstra
2011-01-18 14:25         ` Onkalo Samu
2011-01-19  2:38         ` Yong Zhang
2011-01-19  3:43           ` Mike Galbraith
2011-01-19  4:35             ` Yong Zhang
2011-01-19  5:40               ` Mike Galbraith
2011-01-19  6:09                 ` Yong Zhang
2011-01-19  6:37                   ` Mike Galbraith
2011-01-19  7:19                     ` Ingo Molnar
2011-01-19  7:41                       ` Mike Galbraith
2011-01-19  9:44           ` Peter Zijlstra
2011-01-19 10:38             ` Peter Zijlstra
2011-01-19 11:30               ` Peter Zijlstra
2011-01-19 12:58                 ` Onkalo Samu
2011-01-19 13:13                   ` Onkalo Samu [this message]
2011-01-19 13:30                     ` Peter Zijlstra
2011-01-20  4:18                       ` Yong Zhang
2011-01-20  4:27                         ` Yong Zhang
2011-01-20  5:32                           ` Yong Zhang
2011-01-20  4:59                         ` Mike Galbraith
2011-01-20  5:30                           ` Yong Zhang
2011-01-20  6:12                             ` Mike Galbraith
2011-01-20  7:06                               ` Yong Zhang
2011-01-20  8:37                                 ` Mike Galbraith
2011-01-20  9:07                                   ` Yong Zhang
2011-01-20 10:07                                     ` Mike Galbraith
2011-01-21 11:08                                       ` Peter Zijlstra
2011-01-21 12:24                                         ` Yong Zhang
2011-01-21 13:40                                           ` Peter Zijlstra
2011-01-21 15:03                                             ` Yong Zhang
2011-01-21 15:10                                               ` Peter Zijlstra
2011-01-21 13:15                                       ` Yong Zhang
2011-01-20  7:07                       ` Onkalo Samu
2011-01-21  6:25                         ` Onkalo Samu
2011-01-20  3:10             ` Yong Zhang

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=1295442799.11678.43.camel@kolo \
    --to=samu.p.onkalo@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=yong.zhang0@gmail.com \
    /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