On Thu, 2017-01-12 at 21:27 +0800, Alex Shi wrote: > Kernel or user may have special requirement on cpu response time, > like > if a interrupt is pinned to a cpu, we don't want the cpu goes too > deep > sleep. This patch can prevent this thing happen by consider per cpu > resume_latency setting in cpu sleep state selection in menu governor. > > The pm_qos_resume_latency ask device to give reponse in this time. > That's > similar with cpu cstates' entry_latency + exit_latency. But since > most of cpu cstate either has no entry_latency or add it into > exit_latency > So, we just can restrict this time requirement as states > exit_latency. > > We can set a wanted latency value according to the value of > /sys/devices/system/cpu/cpuX/cpuidle/stateX/latency. to just a bit > less than related state's latency value. Then cpu can get to this > state > or higher. > > Signed-off-by: Alex Shi <alex....@linaro.org> > To: linux-kernel@vger.kernel.org > Cc: linux...@vger.kernel.org > Cc: Ulf Hansson <ulf.hans...@linaro.org> > Cc: Daniel Lezcano <daniel.lezc...@linaro.org> > Cc: Rasmus Villemoes <li...@rasmusvillemoes.dk> > Cc: Arjan van de Ven <ar...@linux.intel.com> > Cc: Rik van Riel <r...@redhat.com> > Cc: "Rafael J. Wysocki" <rafael.j.wyso...@intel.com> >
Acked-by: Rik van Riel <r...@redhat.com> -- All rights reversed
signature.asc
Description: This is a digitally signed message part
