From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: minyard@acm.org, linux-kernel@vger.kernel.org,
Corey Minyard <cminyard@mvista.com>
Subject: Re: [PATCH] sched: Initialize rq->age_stamp on processor start
Date: Tue, 18 Mar 2014 10:25:43 +0100 [thread overview]
Message-ID: <1395134743.4883.72.camel@marge.simpson.net> (raw)
In-Reply-To: <20140318085612.GP25546@laptop.programming.kicks-ass.net>
On Tue, 2014-03-18 at 09:56 +0100, Peter Zijlstra wrote:
> On Tue, Mar 18, 2014 at 05:06:26AM +0100, Mike Galbraith wrote:
> > > +static void __cpuinit set_cpu_rq_start_time(void)
> > > +{
> > > + int cpu = smp_processor_id();
> > > + struct rq *rq = cpu_rq(cpu);
> > > + rq->age_stamp = sched_clock_cpu(cpu);
> > > +}
> >
> > rq->age_stamp must lag rq->clock. See scale_rt_power(), and what
> > happens when it munches magic timewarp mushrooms.
> >
> > > +
> > > static int sched_cpu_active(struct notifier_block *nfb,
> > > unsigned long action, void *hcpu)
> > > {
> > > switch (action & ~CPU_TASKS_FROZEN) {
> > > case CPU_STARTING:
> > > + set_cpu_rq_start_time();
> > > + /* fall through */
> > > case CPU_DOWN_FAILED:
> > > set_cpu_active((long)hcpu, true);
> > > return NOTIFY_OK;
> > > @@ -6922,6 +6931,7 @@ void __init sched_init(void)
> > > init_sched_fair_class();
> > >
> > > scheduler_running = 1;
> > > + set_cpu_rq_start_time();
>
> I would put it one line up; that scheduler_running=1 is the last thing
> we should do.
And set clock and age, dazed scale_rt_power() is butt ugly.
-Mike
next prev parent reply other threads:[~2014-03-18 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 0:05 [PATCH] sched: Initialize rq->age_stamp on processor start minyard
2014-03-18 4:06 ` Mike Galbraith
2014-03-18 8:56 ` Peter Zijlstra
2014-03-18 9:25 ` Mike Galbraith [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-06 19:50 minyard
2014-05-08 16:13 ` Peter Zijlstra
2014-05-08 18:47 ` Corey Minyard
2014-05-08 18:47 ` minyard
2014-05-09 9:12 ` Peter Zijlstra
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=1395134743.4883.72.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox