From: Kunwu Chan <kunwu.chan@linux.dev>
To: paulmck@kernel.org, frederic@kernel.org,
neeraj.upadhyay@kernel.org, joelagnelf@nvidia.com,
josh@joshtriplett.org, boqun@kernel.org, urezki@gmail.com,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
jiangshanlai@gmail.com, qiang.zhang@linux.dev, dave@stgolabs.net
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
Kunwu Chan <kunwu.chan@gmail.com>
Subject: [PATCH v2 0/3] rcu: Improve task-state reporting readability
Date: Fri, 12 Jun 2026 10:34:11 +0800 [thread overview]
Message-ID: <20260612023414.679618-1-kunwu.chan@linux.dev> (raw)
From: Kunwu Chan <kunwu.chan@gmail.com>
This series replaces raw hexadecimal task-state values with
task_state_to_char() output in RCU-related diagnostic messages.
---
Changes in v2:
- Split the original patch into three commits, one per file.
- No code changes.
v1:
https://lore.kernel.org/rcu/442e80e0-4f91-421c-ab68-d26e0a031472@paulmck-laptop/
Based on: linux-rcu repo (dev branch)
URL: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
base-commit: 85bf11e84 ("smp: Make CSD lock acquisition atomic for debug mode")
Kunwu Chan (3):
rcu: Use task_state_to_char() in stall-warning prints
rcutorture: Use task_state_to_char() for task-state reporting
hazptrtorture: Use task_state_to_char() for task-state reporting
kernel/rcu/hazptrtorture.c | 4 ++--
kernel/rcu/rcutorture.c | 4 ++--
kernel/rcu/tree_stall.h | 12 ++++++------
3 files changed, 10 insertions(+), 10 deletions(-)
--
2.43.0
next reply other threads:[~2026-06-12 2:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 2:34 Kunwu Chan [this message]
2026-06-12 2:34 ` [PATCH v2 1/3] rcu: Use task_state_to_char() in stall-warning prints Kunwu Chan
2026-06-12 2:34 ` [PATCH v2 2/3] rcutorture: Use task_state_to_char() for task-state reporting Kunwu Chan
2026-06-12 2:34 ` [PATCH v2 3/3] hazptrtorture: " Kunwu Chan
2026-06-15 18:14 ` [PATCH v2 0/3] rcu: Improve task-state reporting readability Paul E. McKenney
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=20260612023414.679618-1-kunwu.chan@linux.dev \
--to=kunwu.chan@linux.dev \
--cc=boqun@kernel.org \
--cc=dave@stgolabs.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=kunwu.chan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.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