Energy Aware Scheduling (EAS) starts when the scheduling domains are built if the Energy Model (EM) is present. However, in the typical case of Arm/Arm64 systems, the EM is provided after the scheduling domains are first built at boot time, which results in EAS staying disabled.
Fix this issue by re-building the scheduling domain from the arch topology driver, once CPUfreq is up and running and the asymmetry in CPU capacities has been detected. Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org> Signed-off-by: Quentin Perret <quentin.per...@arm.com> --- drivers/base/arch_topology.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c index e7cb0c6ade81..5b9f107f2e4a 100644 --- a/drivers/base/arch_topology.c +++ b/drivers/base/arch_topology.c @@ -10,6 +10,7 @@ #include <linux/arch_topology.h> #include <linux/cpu.h> #include <linux/cpufreq.h> +#include <linux/cpuset.h> #include <linux/device.h> #include <linux/of.h> #include <linux/slab.h> @@ -247,6 +248,7 @@ static void parsing_done_workfn(struct work_struct *work) cpufreq_unregister_notifier(&init_cpu_capacity_notifier, CPUFREQ_POLICY_NOTIFIER); free_cpumask_var(cpus_to_visit); + rebuild_sched_domains(); } #else -- 2.18.0