Merge: sched: Increase sched_tick_remote timeout

MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/7630

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>

Approved-by: Waiman Long <longman@redhat.com>
Approved-by: Herton R. Krzesinski <herton@redhat.com>
Approved-by: CKI KWF Bot <cki-ci-bot+kwf-gitlab-com@redhat.com>

Merged-by: CKI GitLab Kmaint Pipeline Bot <26919896-cki-kmaint-pipeline-bot@users.noreply.gitlab.com>

Author: CKI KWF Bot

kernel/sched/core.c

@@ -5596,7 +5596,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);