From: Tejun Heo <tj@kernel.org>
To: David Dai <david.dai@linux.dev>
Cc: void@manifault.com, arighi@nvidia.com, changwoo@igalia.com,
paulmck@kernel.org, davidai@meta.com, sched-ext@lists.linux.dev,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH] sched_ext, rcu: Eject BPF scheduler on RCU CPU stall panic
Date: Tue, 24 Jun 2025 13:06:10 -1000 [thread overview]
Message-ID: <aFsvYhPTIyQWSFmL@slm.duckdns.org> (raw)
In-Reply-To: <20250624224906.3662221-1-david.dai@linux.dev>
On Tue, Jun 24, 2025 at 03:49:06PM -0700, David Dai wrote:
> For systems using a sched_ext scheduler and has panic_on_rcu_stall
> enabled, try kicking out the current scheduler before issuing a panic.
>
> While there are numerous reasons for RCU CPU stalls that are not
> directly attributed to the scheduler, deferring the panic gives
> sched_ext an opportunity to provide additional debug info when ejecting
> the current scheduler. Also, handling the event more gracefully allows
> us to potentially recover the system instead of incurring additional
> down time.
>
> Suggested-by: Tejun Heo <tj@kernel.org>
> Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
> Signed-off-by: David Dai <david.dai@linux.dev>
Applied to sched_ext/for-6.17.
Thanks.
--
tejun
prev parent reply other threads:[~2025-06-24 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 22:49 [PATCH] sched_ext, rcu: Eject BPF scheduler on RCU CPU stall panic David Dai
2025-06-24 23:06 ` Tejun Heo [this message]
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=aFsvYhPTIyQWSFmL@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=david.dai@linux.dev \
--cc=davidai@meta.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.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.