On 05-03-18, 15:59, Patrick Bellasi wrote:
I personally would really like a solution which do not depend on ordering at all. Meaning, find_best_target should work at its best independently from which CPUs we start from... maybe it can be more or less optimal staring from one CPU or another, but from a functional standpoint is should be the same.
Otherwise we will always risk to have a corner case not covered, as well as make it more difficult to get rid of the star_cpu at a certain point.
There is another thing that I wanted to ask.
With the current state of thing in the EAS-dev kernel + android userspace (cpuset configuration), we want all top-app and foreground tasks to run on the big CPUs however small they might be. That of course causes the big CPUs to wakeup unnecessarily for homescreen and audio playback usecases. And this is by design and not really a bug.
Is it correct to assume that we don't care about being power-efficient for these cases at all as we intentionally place these small tasks on the big CPUs ? I am asking as I am not sure if I should invest time to make EAS-dev kernel to be power efficient for these small foreground tasks, which is exact opposite of what our design is.
-- viresh