> Well, if find_deepest_state() looked at the target residency instead > of the exit latency, this would work I suppose? Unfortunately I don't think this would help - from an OEM system the following target residency values: # cat /sys/devices/system/cpu/cpu0/cpuidle/*/residency 0 2 800 700 > > > In other operating systems the latency values are not validated and this > > does not cause problems by skipping states. > >
