From: "Zqiang" <qiang.zhang@linux.dev>
To: "Joel Fernandes" <joelagnelf@nvidia.com>,
"Donglin Peng" <dolinux.peng@gmail.com>
Cc: paulmck@kernel.org, frederic@kernel.org,
neeraj.upadhyay@kernel.org, rostedt@goodmis.org,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
"Donglin Peng" <pengdonglin@xiaomi.com>
Subject: Re: [PATCH] rcu: Align stall warning 'idle=' output with documentation
Date: Mon, 05 Jan 2026 00:26:54 +0000 [thread overview]
Message-ID: <3188cbf5bcbe5799c77a6cc870ad0ee85b58d255@linux.dev> (raw)
In-Reply-To: <20260104194534.GA2247470@joelbox2>
>
> On Sun, Jan 04, 2026 at 04:10:27PM +0800, Donglin Peng wrote:
>
> >
> > From: Donglin Peng <pengdonglin@xiaomi.com>
> >
> > The RCU stall warning message includes an "idle=" field to indicate
> > the dyntick-idle state of a CPU. According to Documentation/RCU/stallwarn.rst,
> > the hexadecimal number before the first '/' represents the low-order 16
> > bits of the dynticks counter. An even value denotes that the CPU is in
> > dyntick-idle mode, while an odd value indicates otherwise.
> >
> > This was accurate until commit 171476775d32 ("context_tracking: Convert state to atomic_t"),
> > which merged the context tracking state and the dynticks counter into a
> > single atomic value. Consequently, the value printed in the stall warning
> > no longer directly corresponds to the documented dynticks counter bits.
> >
> > To restore consistency between the code's output and the documentation,
> > right-shift the merged atomic state value to extract and display the
> > correct low-order bits of the dynticks counter.
> >
> > Fixes: 171476775d32 ("context_tracking: Convert state to atomic_t")
> > Signed-off-by: Donglin Peng <pengdonglin@xiaomi.com>
> >
> Looks good to me! Also nice use of ilog2() which resolves to a single shift
> right instruction per my testing (shift right of 2).
>
> Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
>
> thanks,
>
> - Joel
>
> >
> > ---
> > kernel/rcu/tree_stall.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/rcu/tree_stall.h b/kernel/rcu/tree_stall.h
> > index b67532cb8770..d25cc826d77a 100644
> > --- a/kernel/rcu/tree_stall.h
> > +++ b/kernel/rcu/tree_stall.h
> > @@ -555,7 +555,7 @@ static void print_cpu_stall_info(int cpu)
> > rdp->rcu_iw_pending ? (int)min(delta, 9UL) + '0' :
> > "!."[!delta],
> > ticks_value, ticks_title,
> > - ct_rcu_watching_cpu(cpu) & 0xffff,
> > + (ct_rcu_watching_cpu(cpu) >> ilog2(CT_RCU_WATCHING)) & 0xffff,
May be also use CT_RCU_WATCHING_START to
replace ilog2(CT_RCU_WATCHING) operations? (I didn't actually test it)
Thanks
Zqiang
> > ct_nesting_cpu(cpu), ct_nmi_nesting_cpu(cpu),
> > rdp->softirq_snap, kstat_softirqs_cpu(RCU_SOFTIRQ, cpu),
> > data_race(rcu_state.n_force_qs) - rcu_state.n_force_qs_gpstart,
> > --
> > 2.34.1
> >
>
next prev parent reply other threads:[~2026-01-05 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 8:10 [PATCH] rcu: Align stall warning 'idle=' output with documentation Donglin Peng
2026-01-04 19:45 ` Joel Fernandes
2026-01-05 0:26 ` Zqiang [this message]
2026-01-05 0:34 ` Joel Fernandes
2026-01-05 1:31 ` Donglin Peng
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=3188cbf5bcbe5799c77a6cc870ad0ee85b58d255@linux.dev \
--to=qiang.zhang@linux.dev \
--cc=dolinux.peng@gmail.com \
--cc=frederic@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=pengdonglin@xiaomi.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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