[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171220145120.vzu5aam5bzw445n5@hirez.programming.kicks-ass.net>
Date: Wed, 20 Dec 2017 15:51:20 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Patrick Bellasi <patrick.bellasi@....com>,
Viresh Kumar <viresh.kumar@...aro.org>,
Ingo Molnar <mingo@...hat.com>, linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
dietmar.eggemann@....com, morten.rasmussen@....com,
juri.lelli@...hat.com, tkjos@...roid.com, joelaf@...gle.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] sched: cpufreq: Keep track of cpufreq utilization
update flags
On Wed, Dec 20, 2017 at 03:47:23PM +0100, Rafael J. Wysocki wrote:
> > Well, we still need flags for crap like IO-WAIT IIRC. That's sugov
> > internal state and not something the scheduler actually already knows.
>
> Not only sugov to be precise, but yes.
Oh, right, intel_pstate also consumes that one..
Powered by blists - more mailing lists