summaryrefslogtreecommitdiff
path: root/drivers/cpuidle/cpuidle-exynos.c
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-10-03 00:42:02 +0300
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-10-04 11:23:37 +0300
commit5f26bdceb9c0a5e6c696aa2899d077cd3ae93413 (patch)
treef73ab5c1133dacafade0cadf06686bd3a8d11a09 /drivers/cpuidle/cpuidle-exynos.c
parent03dba278043358bbbf4f029be169e1e73d2fbe2b (diff)
downloadlinux-5f26bdceb9c0a5e6c696aa2899d077cd3ae93413.tar.xz
cpuidle: menu: Fix wakeup statistics updates for polling state
If the CPU exits the "polling" state due to the time limit in the loop in poll_idle(), this is not a real wakeup and it just means that the "polling" state selection was not adequate. The governor mispredicted short idle duration, but had a more suitable state been selected, the CPU might have spent more time in it. In fact, there is no reason to expect that there would have been a wakeup event earlier than the next timer in that case. Handling such cases as regular wakeups in menu_update() may cause the menu governor to make suboptimal decisions going forward, but ignoring them altogether would not be correct either, because every time menu_select() is invoked, it makes a separate new attempt to predict the idle duration taking distinct time to the closest timer event as input and the outcomes of all those attempts should be recorded. For this reason, make menu_update() always assume that if the "polling" state was exited due to the time limit, the next proper wakeup event for the CPU would be the next timer event (not including the tick). Fixes: a37b969a61c1 "cpuidle: poll_state: Add time limit to poll_idle()" Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Diffstat (limited to 'drivers/cpuidle/cpuidle-exynos.c')
0 files changed, 0 insertions, 0 deletions