Lines Matching refs:EM
10 Energy Model (EM) of the CPUs to select an energy efficient CPU for each task,
23 The actual EM used by EAS is _not_ maintained by the scheduler, but by a
53 The idea behind introducing an EM is to allow the scheduler to evaluate the
56 time, the EM must be as simple as possible to minimize the scheduler latency
60 for the scheduler to decide where a task should run (during wake-up), the EM
83 Model (EM) framework. The EM of a platform is composed of a power cost table
87 The scheduler manages references to the EM objects in the topology code when the
91 em_perf_domain as provided by the EM framework.
117 shared data structure of the EM framework.
131 EAS overrides the CFS task wake-up balancing code. It uses the EM of the
144 'simulate' the task migration. The EM framework provides the em_pd_energy() API
272 CPUs of the system. Thanks to its EM-based design, EAS should cope with them
345 EAS uses the EM of a platform to estimate the impact of scheduling decisions on
346 energy. So, your platform must provide power cost tables to the EM framework in
348 independent EM framework in Documentation/power/energy-model.rst.
351 EM has been registered in order to start EAS.
353 EAS uses the EM to make a forecasting decision on energy usage and thus it is
355 placement. For EAS it doesn't matter whether the EM power values are expressed
362 The task wake-up path is very latency-sensitive. When the EM of a platform is