From: Steven Rostedt <rostedt@goodmis.org>
To: Tejun Heo <tj@kernel.org>
Cc: Shrikanth Hegde <sshegde@linux.ibm.com>,
Valentin Schneider <vschneid@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Kyle McMartin <jkkm@meta.com>
Subject: Re: [PATCH v2] sched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT
Date: Wed, 20 May 2026 15:02:44 -0400 [thread overview]
Message-ID: <20260520150244.0653000a@gandalf.local.home> (raw)
In-Reply-To: <ag34wA_f7OJbJTsb@slm.duckdns.org>
On Wed, 20 May 2026 08:09:04 -1000
Tejun Heo <tj@kernel.org> wrote:
> On Wed, May 20, 2026 at 10:34:35PM +0530, Shrikanth Hegde wrote:
> > By any chance it is running with preempt=none/voluntary?
> > If so it might never call schedule until it goes back to user space.
>
> I think this might be it. In the production dump, the locked up cpus were
> often running btrfs compression / decompression. The kernel is PREEMPT_NONE
> and while that path has resched_curr()'s, with high enough irq frequency, it
> wouldn't be that difficult to catch the cpu enough times before it reaches
> the resched point.
But it should still be making forward progress. The IPI handler is very short.
Are the other CPUs running very short lived RT tasks that constantly
trigger the IPI push logic? I mean it would need to run a lot of RT
tasks that keep going to sleep to cause a IPI storm to trigger.
-- Steve
next prev parent reply other threads:[~2026-05-20 19:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 14:37 Steven Rostedt
2026-05-15 17:17 ` Tejun Heo
2026-05-15 18:38 ` Steven Rostedt
2026-05-15 18:47 ` Tejun Heo
2026-05-15 18:56 ` Steven Rostedt
2026-05-15 22:27 ` Tejun Heo
2026-05-18 8:47 ` Valentin Schneider
2026-05-20 6:33 ` Shrikanth Hegde
2026-05-20 16:52 ` Steven Rostedt
2026-05-20 17:04 ` Shrikanth Hegde
2026-05-20 18:09 ` Tejun Heo
2026-05-20 19:02 ` Steven Rostedt [this message]
2026-05-20 19:37 ` Tejun Heo
2026-05-21 10:11 ` Valentin Schneider
2026-05-20 8:33 ` [tip: sched/core] " tip-bot2 for Steven Rostedt
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=20260520150244.0653000a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jkkm@meta.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®