2 * menu.c - the menu idle governor
4 * Copyright (C) 2006-2007 Adam Belay <abelay@novell.com>
5 * Copyright (C) 2009 Intel Corporation
7 * Arjan van de Ven <arjan@linux.intel.com>
9 * This code is licenced under the GPL version 2 as described
10 * in the COPYING file that acompanies the Linux Kernel.
13 #include <linux/kernel.h>
14 #include <linux/cpuidle.h>
15 #include <linux/pm_qos_params.h>
16 #include <linux/time.h>
17 #include <linux/ktime.h>
18 #include <linux/hrtimer.h>
19 #include <linux/tick.h>
20 #include <linux/sched.h>
21 #include <linux/math64.h>
24 #define RESOLUTION 1024
26 #define MAX_INTERESTING 50000
29 * Concepts and ideas behind the menu governor
31 * For the menu governor, there are 3 decision factors for picking a C
33 * 1) Energy break even point
34 * 2) Performance impact
35 * 3) Latency tolerance (from pmqos infrastructure)
36 * These these three factors are treated independently.
38 * Energy break even point
39 * -----------------------
40 * C state entry and exit have an energy cost, and a certain amount of time in
41 * the C state is required to actually break even on this cost. CPUIDLE
42 * provides us this duration in the "target_residency" field. So all that we
43 * need is a good prediction of how long we'll be idle. Like the traditional
44 * menu governor, we start with the actual known "next timer event" time.
46 * Since there are other source of wakeups (interrupts for example) than
47 * the next timer event, this estimation is rather optimistic. To get a
48 * more realistic estimate, a correction factor is applied to the estimate,
49 * that is based on historic behavior. For example, if in the past the actual
50 * duration always was 50% of the next timer tick, the correction factor will
53 * menu uses a running average for this correction factor, however it uses a
54 * set of factors, not just a single factor. This stems from the realization
55 * that the ratio is dependent on the order of magnitude of the expected
56 * duration; if we expect 500 milliseconds of idle time the likelihood of
57 * getting an interrupt very early is much higher than if we expect 50 micro
58 * seconds of idle time. A second independent factor that has big impact on
59 * the actual factor is if there is (disk) IO outstanding or not.
60 * (as a special twist, we consider every sleep longer than 50 milliseconds
61 * as perfect; there are no power gains for sleeping longer than this)
63 * For these two reasons we keep an array of 12 independent factors, that gets
64 * indexed based on the magnitude of the expected duration as well as the
65 * "is IO outstanding" property.
67 * Limiting Performance Impact
68 * ---------------------------
69 * C states, especially those with large exit latencies, can have a real
70 * noticable impact on workloads, which is not acceptable for most sysadmins,
71 * and in addition, less performance has a power price of its own.
73 * As a general rule of thumb, menu assumes that the following heuristic
75 * The busier the system, the less impact of C states is acceptable
77 * This rule-of-thumb is implemented using a performance-multiplier:
78 * If the exit latency times the performance multiplier is longer than
79 * the predicted duration, the C state is not considered a candidate
80 * for selection due to a too high performance impact. So the higher
81 * this multiplier is, the longer we need to be idle to pick a deep C
82 * state, and thus the less likely a busy CPU will hit such a deep
85 * Two factors are used in determing this multiplier:
86 * a value of 10 is added for each point of "per cpu load average" we have.
87 * a value of 5 points is added for each process that is waiting for
89 * (these values are experimentally determined)
91 * The load average factor gives a longer term (few seconds) input to the
92 * decision, while the iowait value gives a cpu local instantanious input.
93 * The iowait factor may look low, but realize that this is also already
94 * represented in the system load average.
102 unsigned int expected_us
;
104 unsigned int measured_us
;
105 unsigned int exit_us
;
107 u64 correction_factor
[BUCKETS
];
111 #define LOAD_INT(x) ((x) >> FSHIFT)
112 #define LOAD_FRAC(x) LOAD_INT(((x) & (FIXED_1-1)) * 100)
114 static int get_loadavg(void)
116 unsigned long this = this_cpu_load();
119 return LOAD_INT(this) * 10 + LOAD_FRAC(this) / 10;
122 static inline int which_bucket(unsigned int duration
)
127 * We keep two groups of stats; one with no
128 * IO pending, one without.
129 * This allows us to calculate
141 if (duration
< 10000)
143 if (duration
< 100000)
149 * Return a multiplier for the exit latency that is intended
150 * to take performance requirements into account.
151 * The more performance critical we estimate the system
152 * to be, the higher this multiplier, and thus the higher
153 * the barrier to go to an expensive C state.
155 static inline int performance_multiplier(void)
159 /* for higher loadavg, we are more reluctant */
161 mult
+= 2 * get_loadavg();
163 /* for IO wait tasks (per cpu!) we add 5x each */
164 mult
+= 10 * nr_iowait_cpu();
169 static DEFINE_PER_CPU(struct menu_device
, menu_devices
);
171 static void menu_update(struct cpuidle_device
*dev
);
173 /* This implements DIV_ROUND_CLOSEST but avoids 64 bit division */
174 static u64
div_round64(u64 dividend
, u32 divisor
)
176 return div_u64(dividend
+ (divisor
/ 2), divisor
);
180 * menu_select - selects the next idle state to enter
183 static int menu_select(struct cpuidle_device
*dev
)
185 struct menu_device
*data
= &__get_cpu_var(menu_devices
);
186 int latency_req
= pm_qos_requirement(PM_QOS_CPU_DMA_LATENCY
);
190 data
->last_state_idx
= 0;
193 if (data
->needs_update
) {
195 data
->needs_update
= 0;
198 /* Special case when user has set very strict latency requirement */
199 if (unlikely(latency_req
== 0))
202 /* determine the expected residency time, round up */
204 DIV_ROUND_UP((u32
)ktime_to_ns(tick_nohz_get_sleep_length()), 1000);
207 data
->bucket
= which_bucket(data
->expected_us
);
209 multiplier
= performance_multiplier();
212 * if the correction factor is 0 (eg first time init or cpu hotplug
213 * etc), we actually want to start out with a unity factor.
215 if (data
->correction_factor
[data
->bucket
] == 0)
216 data
->correction_factor
[data
->bucket
] = RESOLUTION
* DECAY
;
218 /* Make sure to round up for half microseconds */
219 data
->predicted_us
= div_round64(data
->expected_us
* data
->correction_factor
[data
->bucket
],
223 * We want to default to C1 (hlt), not to busy polling
224 * unless the timer is happening really really soon.
226 if (data
->expected_us
> 5)
227 data
->last_state_idx
= CPUIDLE_DRIVER_STATE_START
;
230 /* find the deepest idle state that satisfies our constraints */
231 for (i
= CPUIDLE_DRIVER_STATE_START
; i
< dev
->state_count
; i
++) {
232 struct cpuidle_state
*s
= &dev
->states
[i
];
234 if (s
->target_residency
> data
->predicted_us
)
236 if (s
->exit_latency
> latency_req
)
238 if (s
->exit_latency
* multiplier
> data
->predicted_us
)
240 data
->exit_us
= s
->exit_latency
;
241 data
->last_state_idx
= i
;
244 return data
->last_state_idx
;
248 * menu_reflect - records that data structures need update
251 * NOTE: it's important to be fast here because this operation will add to
252 * the overall exit latency.
254 static void menu_reflect(struct cpuidle_device
*dev
)
256 struct menu_device
*data
= &__get_cpu_var(menu_devices
);
257 data
->needs_update
= 1;
261 * menu_update - attempts to guess what happened after entry
264 static void menu_update(struct cpuidle_device
*dev
)
266 struct menu_device
*data
= &__get_cpu_var(menu_devices
);
267 int last_idx
= data
->last_state_idx
;
268 unsigned int last_idle_us
= cpuidle_get_last_residency(dev
);
269 struct cpuidle_state
*target
= &dev
->states
[last_idx
];
270 unsigned int measured_us
;
274 * Ugh, this idle state doesn't support residency measurements, so we
275 * are basically lost in the dark. As a compromise, assume we slept
276 * for the whole expected time.
278 if (unlikely(!(target
->flags
& CPUIDLE_FLAG_TIME_VALID
)))
279 last_idle_us
= data
->expected_us
;
282 measured_us
= last_idle_us
;
285 * We correct for the exit latency; we are assuming here that the
286 * exit latency happens after the event that we're interested in.
288 if (measured_us
> data
->exit_us
)
289 measured_us
-= data
->exit_us
;
292 /* update our correction ratio */
294 new_factor
= data
->correction_factor
[data
->bucket
]
295 * (DECAY
- 1) / DECAY
;
297 if (data
->expected_us
> 0 && data
->measured_us
< MAX_INTERESTING
)
298 new_factor
+= RESOLUTION
* measured_us
/ data
->expected_us
;
301 * we were idle so long that we count it as a perfect
304 new_factor
+= RESOLUTION
;
307 * We don't want 0 as factor; we always want at least
308 * a tiny bit of estimated time.
313 data
->correction_factor
[data
->bucket
] = new_factor
;
317 * menu_enable_device - scans a CPU's states and does setup
320 static int menu_enable_device(struct cpuidle_device
*dev
)
322 struct menu_device
*data
= &per_cpu(menu_devices
, dev
->cpu
);
324 memset(data
, 0, sizeof(struct menu_device
));
329 static struct cpuidle_governor menu_governor
= {
332 .enable
= menu_enable_device
,
333 .select
= menu_select
,
334 .reflect
= menu_reflect
,
335 .owner
= THIS_MODULE
,
339 * init_menu - initializes the governor
341 static int __init
init_menu(void)
343 return cpuidle_register_governor(&menu_governor
);
347 * exit_menu - exits the governor
349 static void __exit
exit_menu(void)
351 cpuidle_unregister_governor(&menu_governor
);
354 MODULE_LICENSE("GPL");
355 module_init(init_menu
);
356 module_exit(exit_menu
);