From: Ingo Molnar <mingo@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Steve Muckle <steve.muckle@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH] sched/fair: Invoke cpufreq hooks for CONFIG_SMP unset
Date: Tue, 10 May 2016 10:13:01 +0200 [thread overview]
Message-ID: <20160510081301.GA16790@gmail.com> (raw)
In-Reply-To: <2440649.iyOucdARxJ@vostro.rjw.lan>
* Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> On Monday, May 09, 2016 04:53:16 PM Steve Muckle wrote:
> > On Sat, May 07, 2016 at 08:30:51AM +0200, Ingo Molnar wrote:
> > >
> > > * Peter Zijlstra <peterz@infradead.org> wrote:
> > >
> > > > On Fri, May 06, 2016 at 02:58:43PM +0200, Rafael J. Wysocki wrote:
> > > > > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > > >
> > > > > Commit 34e2c555f3e1 (cpufreq: Add mechanism for registering utilization
> > > > > update callbacks) overlooked the fact that update_load_avg(), where
> > > > > CFS invokes cpufreq utilization update hooks, becomes an empty stub for
> > > > > CONFIG_SMP unset. In consequence, if CONFIG_SMP is not set, cpufreq
> > > > > governors are never invoked from CFS and they do not have a chance to
> > > > > evaluate CPU performace levels and update them often enough. Needless
> > > > > to say, things don't work as expected then.
> > > > >
> > > > > Fix the problem by making the !CONFIG_SMP stub of update_load_avg()
> > > > > invoke cpufreq update hooks too.
> > > > >
> > > > > Fixes: 34e2c555f3e1 (cpufreq: Add mechanism for registering utilization update callbacks)
> > > > > Reported-by: Steve Muckle <steve.muckle@linaro.org>
> > > > > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > >
> > > > Rafael; feel free to push this through the pm tree.
> > > >
> > > > Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > >
> > > I already have it in sched/urgent.
> >
> > Looks like this just missed 4.6-rc7 and the release email for
> > that doesn't suggest an rc8, as it stands...
>
> But the final 4.6 will be released on Sunday or so and there are a few days left
> still.
Yeah, I'll send the sched/urgent bits to Linus later today.
Thanks,
Ingo
next prev parent reply other threads:[~2016-05-10 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 12:58 [PATCH] sched/fair: Invoke cpufreq hooks for CONFIG_SMP unset Rafael J. Wysocki
2016-05-06 19:08 ` Steve Muckle
2016-05-06 19:36 ` Rafael J. Wysocki
2016-05-07 6:13 ` Peter Zijlstra
2016-05-07 6:30 ` Ingo Molnar
2016-05-09 8:30 ` Peter Zijlstra
2016-05-09 23:53 ` Steve Muckle
2016-05-09 23:58 ` Rafael J. Wysocki
2016-05-10 8:13 ` Ingo Molnar [this message]
2016-05-07 6:37 ` [tip:sched/urgent] sched/fair: Fix !CONFIG_SMP kernel cpufreq governor breakage tip-bot for Rafael J. Wysocki
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=20160510081301.GA16790@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=steve.muckle@linaro.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).