From: Stefan <stefan@pimaker.at>
To: paulmck@kernel.org
Cc: rcu@vger.kernel.org, Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu/nocb: Fix dump_tree hierarchy print always active
Date: Mon, 07 Oct 2019 17:56:33 +0000 [thread overview]
Message-ID: <d74644c4-9bdc-a21c-acc2-a8f525863064@pimaker.at> (raw)
In-Reply-To: <20191007012625.GA23446@paulmck-ThinkPad-P72>
On 07/10/2019 03:26, Paul E. McKenney wrote:
>
> On Fri, Oct 04, 2019 at 03:24:02PM -0700, Paul E. McKenney wrote:
>> On Fri, Oct 04, 2019 at 07:49:10PM +0000, Stefan Reiter wrote:
>>> Commit 18cd8c93e69e ("rcu/nocb: Print gp/cb kthread hierarchy if
>>> dump_tree") added print statements to rcu_organize_nocb_kthreads for
>>> debugging, but incorrectly guarded them, causing the function to always
>>> spew out its message.
>>>
>>> This patch fixes it by guarding both pr_alert statements with dump_tree,
>>> while also changing the second pr_alert to a pr_cont, to print the
>>> hierarchy in a single line (assuming that's how it was supposed to
>>> work).
>>>
>>> Fixes: 18cd8c93e69e ("rcu/nocb: Print gp/cb kthread hierarchy if dump_tree")
>>> Signed-off-by: Stefan Reiter <stefan@pimaker.at>
>>
>> Queued for testing and review, thank you!
>
> And here is an updated version to make the special case of a nocb GP
> kthread having no other nocb CB kthreads look less strange. Does this
> work for you?
Tested just now, works for me. Thanks for the additional fix!
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> commit e6223b0705369750990c32ddc80251942e61be30
> Author: Stefan Reiter <stefan@pimaker.at>
> Date: Fri Oct 4 19:49:10 2019 +0000
>
> rcu/nocb: Fix dump_tree hierarchy print always active
>
> Commit 18cd8c93e69e ("rcu/nocb: Print gp/cb kthread hierarchy if
> dump_tree") added print statements to rcu_organize_nocb_kthreads for
> debugging, but incorrectly guarded them, causing the function to always
> spew out its message.
>
> This patch fixes it by guarding both pr_alert statements with dump_tree,
> while also changing the second pr_alert to a pr_cont, to print the
> hierarchy in a single line (assuming that's how it was supposed to
> work).
>
> Fixes: 18cd8c93e69e ("rcu/nocb: Print gp/cb kthread hierarchy if dump_tree")
> Signed-off-by: Stefan Reiter <stefan@pimaker.at>
> [ paulmck: Make single-nocbs-CPU GP kthreads look less erroneous. ]
> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
>
> diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
> index d5334e4..d43f4e0 100644
> --- a/kernel/rcu/tree_plugin.h
> +++ b/kernel/rcu/tree_plugin.h
> @@ -2295,6 +2295,8 @@ static void __init rcu_organize_nocb_kthreads(void)
> {
> int cpu;
> bool firsttime = true;
> + bool gotnocbs = false;
> + bool gotnocbscbs = true;
> int ls = rcu_nocb_gp_stride;
> int nl = 0; /* Next GP kthread. */
> struct rcu_data *rdp;
> @@ -2317,21 +2319,31 @@ static void __init rcu_organize_nocb_kthreads(void)
> rdp = per_cpu_ptr(&rcu_data, cpu);
> if (rdp->cpu >= nl) {
> /* New GP kthread, set up for CBs & next GP. */
> + gotnocbs = true;
> nl = DIV_ROUND_UP(rdp->cpu + 1, ls) * ls;
> rdp->nocb_gp_rdp = rdp;
> rdp_gp = rdp;
> - if (!firsttime && dump_tree)
> - pr_cont("\n");
> - firsttime = false;
> - pr_alert("%s: No-CB GP kthread CPU %d:", __func__, cpu);
> + if (dump_tree) {
> + if (!firsttime)
> + pr_cont("%s\n", gotnocbscbs
> + ? "" : " (self only)");
> + gotnocbscbs = false;
> + firsttime = false;
> + pr_alert("%s: No-CB GP kthread CPU %d:",
> + __func__, cpu);
> + }
> } else {
> /* Another CB kthread, link to previous GP kthread. */
> + gotnocbscbs = true;
> rdp->nocb_gp_rdp = rdp_gp;
> rdp_prev->nocb_next_cb_rdp = rdp;
> - pr_alert(" %d", cpu);
> + if (dump_tree)
> + pr_cont(" %d", cpu);
> }
> rdp_prev = rdp;
> }
> + if (gotnocbs && dump_tree)
> + pr_cont("%s\n", gotnocbscbs ? "" : " (self only)");
> }
>
> /*
>
prev parent reply other threads:[~2019-10-07 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 19:49 [PATCH] rcu/nocb: Fix dump_tree hierarchy print always active Stefan Reiter
2019-10-04 22:24 ` Paul E. McKenney
2019-10-07 1:26 ` Paul E. McKenney
2019-10-07 17:56 ` Stefan [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=d74644c4-9bdc-a21c-acc2-a8f525863064@pimaker.at \
--to=stefan@pimaker.at \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).