[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52613B0B.4050000@linux.intel.com>
Date: Fri, 18 Oct 2013 06:43:39 -0700
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Morten Rasmussen <morten.rasmussen@....com>
CC: Peter Zijlstra <peterz@...radead.org>,
"mingo@...nel.org" <mingo@...nel.org>,
"pjt@...gle.com" <pjt@...gle.com>, "rjw@...k.pl" <rjw@...k.pl>,
"dirk.j.brandewie@...el.com" <dirk.j.brandewie@...el.com>,
"vincent.guittot@...aro.org" <vincent.guittot@...aro.org>,
"alex.shi@...aro.org" <alex.shi@...aro.org>,
"preeti@...ux.vnet.ibm.com" <preeti@...ux.vnet.ibm.com>,
"efault@....de" <efault@....de>, "corbet@....net" <corbet@....net>,
"tglx@...utronix.de" <tglx@...utronix.de>,
Catalin Marinas <Catalin.Marinas@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>
Subject: Re: [RFC][PATCH 4/7] sched: power: Remove power capacity hints for
kworker threads
>
> We should be able to boil it down to a sequence on ARM as well. But it
> means dropping cpufreq and looking at the clock framework.
>
> Are you still using the pre- and post-change notifiers on Intel, or can
> they be ignored safely?
we do not use change notifiers
(since the hardware changes frequency independently of what "p state" we asked for
frequently and in many very common conditions, even if anything depended on being notified on changes...
it couldn't possibly work anyway)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists