From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Zqiang <qiang1.zhang@intel.com>, paulmck@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rcu: Add per-CPU rcuc task info to RCU CPU stall warnings
Date: Mon, 24 Jan 2022 17:03:58 +0700 [thread overview]
Message-ID: <ec15ce1f-4766-6ccc-97d2-980c8ea183a7@gnuweeb.org> (raw)
In-Reply-To: <20220124103637.4001386-1-qiang1.zhang@intel.com>
Hi Zqiang,
On Sat, 22 Jan 2022 02:30:00 +0800, Zqiang <qiang1.zhang@intel.com> wrote:
```
> +static void rcuc_kthread_dump(struct rcu_data *rdp)
> +{
> + int cpu;
> + unsigned long j;
> + struct task_struct *rcuc = rdp->rcu_cpu_kthread_task;
> +
> + if (rcu_is_rcuc_kthread_starving(rdp, &j)) {
> + cpu = rcuc ? task_cpu(rcuc) : -1;
> +
> + if (rcuc) {
> + pr_err("%s kthread starved for %ld jiffies, stack dump:\n",
> + rcuc->comm, j);
> + sched_show_task(rcuc);
> + if (cpu >= 0) {
> + if (cpu_online(cpu) && !idle_cpu(cpu)) {
> + pr_err("Dump current CPU stack:\n");
> + if (!trigger_single_cpu_backtrace(cpu))
> + dump_cpu_task(cpu);
> + }
> + }
> + }
> + }
> +}
```
1) We can reduce the nested if with an early return
after checking `rcu_is_rcuc_kthread_starving()`.
2) This ternary operator doesn't make sense:
`cpu = rcuc ? task_cpu(rcuc) : -1;`
If `rcuc` is NULL, then the "if (rcuc)" block will never
be executed, and `cpu` variable won't be used, why should
we perform a conditional with ternary to assign -1 here?
3) We can use an early return as well for the `if (rcuc)` to
avoid more nested if.
FWIW, this one makes more sense:
```
static void rcuc_kthread_dump(struct rcu_data *rdp)
{
int cpu;
unsigned long j;
struct task_struct *rcuc;
if (!rcu_is_rcuc_kthread_starving(rdp, &j))
return;
rcuc = rdp->rcu_cpu_kthread_task;
if (!rcuc)
return;
pr_err("%s kthread starved for %ld jiffies, stack dump:\n", rcuc->comm, j);
sched_show_task(rcuc);
cpu = task_cpu(rcuc);
if (cpu_online(cpu) && !idle_cpu(cpu)) {
pr_err("Dump current CPU stack:\n");
if (!trigger_single_cpu_backtrace(cpu))
dump_cpu_task(cpu);
}
}
```
Thank you!
--
Ammar Faizi
next prev parent reply other threads:[~2022-01-24 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 10:36 Zqiang
2022-01-24 10:03 ` Ammar Faizi [this message]
2022-01-24 10:38 ` Ammar Faizi
2022-01-24 16:42 ` Paul E. McKenney
2022-01-24 22:08 ` Ammar Faizi
2022-01-25 2:24 ` Zhang, Qiang1
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=ec15ce1f-4766-6ccc-97d2-980c8ea183a7@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang1.zhang@intel.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®