When schedutil looks at the CPU utilization, the current PELT value forthat CPU is returned straight away. In certain scenarios this can haveundesired side effects and delays on frequency selection.

For example, since the task utilization is decayed at wakeup time, along sleeping big task newly enqueued does not add immediately asignificant contribution to the target CPU. This introduces some latencybefore schedutil will be able to detect the best frequency required bythat task.

Moreover, the PELT signal build-up time is a function of the currentfrequency, because of the scale invariant load tracking support. Thus,starting from a lower frequency, the utilization build-up time willincrease even more and further delays the selection of the actualfrequency which better serves the task requirements.

In order to reduce this kind of latencies, we integrate the usageof the CPU's estimated utilization in the sugov_get_util function.This allows to properly consider the expected utilization of a CPU which,for example, has just got a big task running after a long sleep period.Ultimately this allows to select the best frequency to run a taskright after its wake-up.