Re: [PATCH] sched: Increase sched_tick_remote timeout
From: Phil Auld
Date: Tue Sep 23 2025 - 06:47:55 EST
Hi,
On Thu, Sep 11, 2025 at 12:13:00PM -0400 Phil Auld wrote:
> 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.
>
> Signed-off-by: Phil Auld <pauld@xxxxxxxxxx>
> Suggested-by: Frederic Weisbecker <frederic@xxxxxxxxxx>
> Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
> Cc: Frederic Weisbecker <frederic@xxxxxxxxxx>
Frederic ack'd this. Any other thoughts or opinions on this one
character patch?
Cheers,
Phil
> ---
> kernel/sched/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index be00629f0ba4..ef90d358252d 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -5724,7 +5724,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);
>
> --
> 2.51.0
>
--