From: Frederic Weisbecker <frederic@kernel.org>
To: Phil Auld <pauld@redhat.com>
Cc: bsegall@google.com, dietmar.eggemann@arm.com,
juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
rostedt@goodmis.org, tanghui20@huawei.com, tglx@linutronix.de,
vincent.guittot@linaro.org, wangtao554@huawei.com,
zhangqiao22@huawei.com, Waiman Long <longman@redhat.com>
Subject: Re: [PATCH] sched: Increase sched_tick_remote timeout
Date: Thu, 11 Sep 2025 18:29:09 +0200 [thread overview]
Message-ID: <aML41e2csdTdSTNU@localhost.localdomain> (raw)
In-Reply-To: <20250911161300.437944-1-pauld@redhat.com>
Le Thu, Sep 11, 2025 at 12:13:00PM -0400, Phil Auld a écrit :
> 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@redhat.com>
> Suggested-by: Frederic Weisbecker <frederic@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Frederic Weisbecker <frederic@kernel.org>
Acked-by: Frederic Weisbecker <frederic@kernel.org>
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2025-09-11 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 12:42 [PATCH] sched/core: Fix potential deadlock on rq lock Wang Tao
2025-09-11 13:53 ` Peter Zijlstra
2025-09-11 15:02 ` Frederic Weisbecker
2025-09-11 15:14 ` Phil Auld
2025-09-11 15:38 ` Frederic Weisbecker
2025-09-11 16:13 ` [PATCH] sched: Increase sched_tick_remote timeout Phil Auld
2025-09-11 16:29 ` Frederic Weisbecker [this message]
2025-09-17 6:26 ` wangtao (EQ)
2025-09-16 8:44 ` wangtao (EQ)
2025-09-16 12:49 ` Phil Auld
2025-09-23 10:47 ` Phil Auld
2025-10-10 12:13 ` Phil Auld
2025-11-03 21:56 ` Phil Auld
2025-11-14 12:19 ` [tip: sched/core] " tip-bot2 for Phil Auld
2025-11-14 13:07 ` Phil Auld
2025-11-17 16:23 ` tip-bot2 for Phil Auld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aML41e2csdTdSTNU@localhost.localdomain \
--to=frederic@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tanghui20@huawei.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=wangtao554@huawei.com \
--cc=zhangqiao22@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.