From: John Ogness <john.ogness@linutronix.de>
To: Zhouyi Zhou <zhouzhouyi@gmail.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
npiggin@gmail.com, ldufour@linux.ibm.com, pmladek@suse.com,
Julia.Lawall@inria.fr, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, lance@osuosl.org,
paulmck@kernel.org, rcu@vger.kernel.org
Cc: Zhouyi Zhou <zhouzhouyi@gmail.com>
Subject: Re: [PATCH linux-next] powerpc: use raw_smp_processor_id in arch_touch_nmi_watchdog
Date: Thu, 14 Jul 2022 11:31:00 +0206 [thread overview]
Message-ID: <87tu7k6o7n.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20220714013131.12648-1-zhouzhouyi@gmail.com>
On 2022-07-14, Zhouyi Zhou <zhouzhouyi@gmail.com> wrote:
> use raw_smp_processor_id() in arch_touch_nmi_watchdog
> because when called from watchdog, the cpu is preemptible.
I would expect the correct solution is to make it a non-migration
section. Something like the below (untested) patch.
John Ogness
diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c
index bfc27496fe7e..9d34aa809241 100644
--- a/arch/powerpc/kernel/watchdog.c
+++ b/arch/powerpc/kernel/watchdog.c
@@ -450,17 +450,23 @@ static enum hrtimer_restart watchdog_timer_fn(struct hrtimer *hrtimer)
void arch_touch_nmi_watchdog(void)
{
unsigned long ticks = tb_ticks_per_usec * wd_timer_period_ms * 1000;
- int cpu = smp_processor_id();
+ int cpu;
u64 tb;
- if (!cpumask_test_cpu(cpu, &watchdog_cpumask))
+ cpu = get_cpu();
+
+ if (!cpumask_test_cpu(cpu, &watchdog_cpumask)) {
+ goto out;
return;
+ }
tb = get_tb();
if (tb - per_cpu(wd_timer_tb, cpu) >= ticks) {
per_cpu(wd_timer_tb, cpu) = tb;
wd_smp_clear_cpu_pending(cpu);
}
+out:
+ put_cpu();
}
EXPORT_SYMBOL(arch_touch_nmi_watchdog);
next prev parent reply other threads:[~2022-07-14 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 1:31 [PATCH linux-next] powerpc: use raw_smp_processor_id in arch_touch_nmi_watchdog Zhouyi Zhou
2022-07-14 9:25 ` John Ogness [this message]
2022-07-14 10:01 ` Zhouyi Zhou
2022-07-14 10:01 ` Zhouyi Zhou
2022-07-14 11:46 ` John Ogness
2022-07-14 11:46 ` John Ogness
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=87tu7k6o7n.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=Julia.Lawall@inria.fr \
--cc=benh@kernel.crashing.org \
--cc=lance@osuosl.org \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulmck@kernel.org \
--cc=paulus@samba.org \
--cc=pmladek@suse.com \
--cc=rcu@vger.kernel.org \
--cc=zhouzhouyi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.