kernel/sched/fair.c

6718 	 * if energy aware scheduler is being used
7807  * energy_env - Utilization landscape for energy estimation.
7850  * energy cost is removed (by cpu_util()) and must be calculated
7929  * compute_energy(): Use the Energy Model to estimate the energy that @pd would
7939 	unsigned long energy;
7944 	energy = em_cpu_energy(pd->em_pd, max_util, busy_time, eenv->cpu_cap);
7946 	trace_sched_compute_energy_tp(p, dst_cpu, energy, max_util, busy_time);
7948 	return energy;
7952  * find_energy_efficient_cpu(): Find most energy-efficient target CPU for the
7956  * out which of the CPU candidates is the most energy-efficient.
7959  * all the most energy efficient CPU candidates (according to the Energy
7968  * In practice, it could be preferable from an energy standpoint to pack
7975  * of the energy savings of EAS come from the asymmetry of the system, and
7980  * NOTE: Forkees are not accepted in the energy-aware wake-up path because
7982  * forecast their impact on energy consumption. Consequently, they will be
7984  * to be energy-inefficient in some use-cases. The alternative would be to
8042 		/* Account external pressure for the energy estimation */
8112 		/* Compute the 'base' energy of the pd, without @p */
8115 		/* Evaluate the energy impact of using prev_cpu. */
8127 		/* Evaluate the energy impact of using max_spare_cap_cpu. */
8129 			/* Current best energy cpu fits better */
8135 			 * but best energy cpu has better capacity.
8149 			 * Both fit for the task but best energy cpu has lower
8150 			 * energy impact.
10165 	 * throughput. Maximize throughput, power/energy consequences are not