[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170327180941.3z7i5wurvsg3bmia@sirena.org.uk>
Date: Mon, 27 Mar 2017 19:09:41 +0100
From: Mark Brown <broonie@...nel.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Juri Lelli <juri.lelli@....com>,
Peter Zijlstra <peterz@...radead.org>, mingo@...hat.com,
viresh.kumar@...aro.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, tglx@...utronix.de,
vincent.guittot@...aro.org, rostedt@...dmis.org,
luca.abeni@...tannapisa.it, claudio@...dence.eu.com,
tommaso.cucinotta@...tannapisa.it, bristot@...hat.com,
mathieu.poirier@...aro.org, tkjos@...roid.com, joelaf@...gle.com,
andresoportus@...gle.com, morten.rasmussen@....com,
dietmar.eggemann@....com, patrick.bellasi@....com,
Ingo Molnar <mingo@...nel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: [RFD PATCH 3/5] sched/cpufreq_schedutil: make worker kthread be
SCHED_DEADLINE
On Mon, Mar 27, 2017 at 07:37:39PM +0200, Rafael J. Wysocki wrote:
> One is that if we want *all* drivers to work with schedutil, we need to keep
> the kthread for the ones that will never be reworked (because nobody cares
> etc). But then perhaps the kthread implementation may be left alone (because
> nobody cares etc).
A very large proportion of the affected code (at least once you get into
the realm of talking to the PMICs) is shared in core code in various
subsystems rather than in individual drivers so the problem might be
tractable.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists