From: Neeraj Upadhyay <Neeraj.Upadhyay@kernel.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>,
rcu@vger.kernel.org
Subject: Re: [PATCH] doc: rcu: update printed dynticks counter bits
Date: Fri, 27 Sep 2024 12:20:25 +0530 [thread overview]
Message-ID: <20240927065025.GA2649@neeraj.linux> (raw)
In-Reply-To: <87cykq23a5.fsf@tarshish>
Hi Baruch,
On Thu, Sep 26, 2024 at 12:05:38PM +0300, Baruch Siach wrote:
> Hi Paul,
>
> On Tue, Aug 20 2024, Paul E. McKenney wrote:
> > On Sun, Aug 18, 2024 at 11:18:17AM +0300, Baruch Siach wrote:
> >> The stall warning prints 16 bits since commit 171476775d32
> >> ("context_tracking: Convert state to atomic_t").
> >>
> >> Fixes: 171476775d32 ("context_tracking: Convert state to atomic_t")
> >> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> >
> > Good eyes!
> >
> > Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
>
> I remember seeing this patch queued in one of the rcu git trees, but I
> can't find it anymore. I don't see it in Linus' tree either.
>
This patch is included for v6.13 queue [1]
[1] https://git.kernel.org/pub/scm/linux/kernel/git/neeraj.upadhyay/linux-rcu.git/log/?h=dev
- Neeraj
> Thanks,
> baruch
>
> >> Documentation/RCU/stallwarn.rst | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/Documentation/RCU/stallwarn.rst b/Documentation/RCU/stallwarn.rst
> >> index ca7b7cd806a1..30080ff6f406 100644
> >> --- a/Documentation/RCU/stallwarn.rst
> >> +++ b/Documentation/RCU/stallwarn.rst
> >> @@ -249,7 +249,7 @@ ticks this GP)" indicates that this CPU has not taken any scheduling-clock
> >> interrupts during the current stalled grace period.
> >>
> >> The "idle=" portion of the message prints the dyntick-idle state.
> >> -The hex number before the first "/" is the low-order 12 bits of the
> >> +The hex number before the first "/" is the low-order 16 bits of the
> >> dynticks counter, which will have an even-numbered value if the CPU
> >> is in dyntick-idle mode and an odd-numbered value otherwise. The hex
> >> number between the two "/"s is the value of the nesting, which will be
> >> --
> >> 2.43.0
> >>
>
> --
> ~. .~ Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
> - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
prev parent reply other threads:[~2024-09-27 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 8:18 [PATCH] doc: rcu: update printed dynticks counter bits Baruch Siach
2024-08-20 18:47 ` Paul E. McKenney
2024-09-26 9:05 ` Baruch Siach
2024-09-27 6:50 ` Neeraj Upadhyay [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=20240927065025.GA2649@neeraj.linux \
--to=neeraj.upadhyay@kernel.org \
--cc=baruch@tkos.co.il \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--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