From 34418fc16ee38e61cd135717b464d9e792925ea0 Mon Sep 17 00:00:00 2001 From: Olav Haugan Date: Mon, 17 Oct 2016 17:05:54 -0700 Subject: [PATCH] sched/fair: Fix issue with trace flag not being set properly During scheduler boost the sched_task_load ftrace event might not log the correct flag value. Ensure that the flag is always initialized with the selected cluster information. Change-Id: Ia986d0fbc512c8e9ed1b5fb5b2ac4bc564cc4ba9 Signed-off-by: Olav Haugan --- kernel/sched/fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 6362b864e2b1..98ae45174a40 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -3189,8 +3189,8 @@ retry: } } p->last_cpu_selected_ts = sched_ktime_clock(); - sbc_flag |= env.sbc_best_cluster_flag; out: + sbc_flag |= env.sbc_best_cluster_flag; rcu_read_unlock(); trace_sched_task_load(p, sched_boost(), env.reason, env.sync, env.need_idle, sbc_flag, target);