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 <frederic@kernel.org>
Signed-off-by: Phil Auld <pauld@redhat.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Frederic Weisbecker <frederic@kernel.org>
Link: https://patch.msgid.link/20250911161300.437944-1-pauld@redhat.com

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 68f19aacfdc647767b5bbdeffdc385abbc2f8cb1..699db3f46df6469ba59fe6b91450330f2e751aea 100644 (file)
--- 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);