From: Phil Auld Date: Thu, 11 Sep 2025 16:13:00 +0000 (-0400) Subject: sched: Increase sched_tick_remote timeout X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=aaab6bb54ab9bc4c37ff33b816031918d2760517;p=thirdparty%2Flinux.git sched: Increase sched_tick_remote timeout Increase the sched_tick_remote WARN_ON timeout to remove false positives due to temporarily busy HK cpus. The suggestion was 30 seconds to catch really stuck remote tick processing but not trigger it too easily. Suggested-by: Frederic Weisbecker Signed-off-by: Phil Auld Signed-off-by: Peter Zijlstra (Intel) Acked-by: Frederic Weisbecker Link: https://patch.msgid.link/20250911161300.437944-1-pauld@redhat.com --- diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 68f19aacfdc64..699db3f46df64 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -5619,7 +5619,7 @@ static void sched_tick_remote(struct work_struct *work) * reasonable amount of time. */ u64 delta = rq_clock_task(rq) - curr->se.exec_start; - WARN_ON_ONCE(delta > (u64)NSEC_PER_SEC * 3); + WARN_ON_ONCE(delta > (u64)NSEC_PER_SEC * 30); } curr->sched_class->task_tick(rq, curr, 0);