[lkml]   [2019]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[tip: sched/urgent] sched/core: Remove double update_max_interval() call on CPU startup
The following commit has been merged into the sched/urgent branch of tip:

Commit-ID: 9fc41acc89e58262c917b4be89ef00a87485804f
Author: Valentin Schneider <>
AuthorDate: Mon, 23 Sep 2019 10:30:17 +01:00
Committer: Ingo Molnar <>
CommitterDate: Wed, 25 Sep 2019 17:42:32 +02:00

sched/core: Remove double update_max_interval() call on CPU startup

update_max_interval() is called in both CPUHP_AP_SCHED_STARTING's startup
and teardown callbacks, but it turns out it's also called at the end of
the startup callback of CPUHP_AP_ACTIVE (which is further down the
startup sequence).

There's no point in repeating this interval update in the startup sequence
since the CPU will remain online until it goes down the teardown path.

Remove the redundant call in sched_cpu_activate() (CPUHP_AP_ACTIVE).

Signed-off-by: Valentin Schneider <>
Signed-off-by: Peter Zijlstra (Intel) <>
Cc: Linus Torvalds <>
Cc: Peter Zijlstra <>
Cc: Thomas Gleixner <>
Signed-off-by: Ingo Molnar <>
kernel/sched/core.c | 2 --
1 file changed, 2 deletions(-)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 00ef44c..1b61cf4 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6425,8 +6425,6 @@ int sched_cpu_activate(unsigned int cpu)
rq_unlock_irqrestore(rq, &rf);

- update_max_interval();
return 0;

 \ /
  Last update: 2019-09-27 10:11    [W:0.038 / U:2.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site