Skip to content

Commit 89920be

Browse files
committed
sched: Increase sched_tick_remote timeout
JIRA: https://issues.redhat.com/browse/RHEL-102425 Upstream Status: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core commit aaab6bb Author: Phil Auld <pauld@redhat.com> Date: Thu Sep 11 12:13:00 2025 -0400 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 Signed-off-by: Phil Auld <pauld@redhat.com>
1 parent 0dd464a commit 89920be

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

kernel/sched/core.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5596,7 +5596,7 @@ static void sched_tick_remote(struct work_struct *work)
55965596
* reasonable amount of time.
55975597
*/
55985598
u64 delta = rq_clock_task(rq) - curr->se.exec_start;
5599-
WARN_ON_ONCE(delta > (u64)NSEC_PER_SEC * 3);
5599+
WARN_ON_ONCE(delta > (u64)NSEC_PER_SEC * 30);
56005600
}
56015601
curr->sched_class->task_tick(rq, curr, 0);
56025602

0 commit comments

Comments
 (0)