From: Changwoo Min <changwoo@igalia.com>
To: tj@kernel.org, void@manifault.com, arighi@nvidia.com,
changwoo@igalia.com
Cc: kernel-dev@igalia.com, sched-ext@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] sched_ext: Improve watchdog stall diagnostics
Date: Wed, 8 Apr 2026 12:11:11 +0900 [thread overview]
Message-ID: <20260408031113.76005-1-changwoo@igalia.com> (raw)
When a watchdog timeout fires on a system with many CPUs, the per-CPU
state dump in the exit info can get truncated. If the stall CPU happens
to be in the middle or end of the CPU list, its state may never appear
in the output, making it difficult to diagnose the hang.
This series addresses that by always dumping the stall CPU first.
Patch 1 is a preparatory refactor that extracts the per-CPU dump logic
into a scx_dump_cpu() helper, making patch 2 straightforward.
Patch 2 adds a stall_cpu field to scx_exit_info, threads it through
the exit path, and reorders the dump loop to emit the stall CPU before
all others.
Changwoo Min (2):
sched_ext: Extract scx_dump_cpu() from scx_dump_state()
sched_ext: Dump the stall CPU first in watchdog exit
kernel/sched/ext.c | 202 +++++++++++++++++++-----------------
kernel/sched/ext_internal.h | 3 +
2 files changed, 112 insertions(+), 93 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-08 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 3:11 Changwoo Min [this message]
2026-04-08 3:11 ` [PATCH 1/2] sched_ext: Extract scx_dump_cpu() from scx_dump_state() Changwoo Min
2026-04-08 3:11 ` [PATCH 2/2] sched_ext: Dump the stall CPU first in watchdog exit Changwoo Min
2026-04-09 1:19 ` Tejun Heo
2026-04-09 5:52 ` Andrea Righi
2026-04-09 6:28 ` Tejun Heo
2026-04-11 12:28 ` Changwoo Min
2026-04-09 5:44 ` Andrea Righi
2026-04-11 14:37 ` Changwoo Min
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=20260408031113.76005-1-changwoo@igalia.com \
--to=changwoo@igalia.com \
--cc=arighi@nvidia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--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 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®