From: Anton Blanchard <anton@ozlabs.org>
To: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
npiggin@gmail.com, mikey@neuling.org, oohall@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 2/2] powerpc/time: Only cap decrementer when watchdog is enabled
Date: Sat, 29 Sep 2018 11:26:07 +1000 [thread overview]
Message-ID: <20180929012607.10204-2-anton@ozlabs.org> (raw)
In-Reply-To: <20180929012607.10204-1-anton@ozlabs.org>
If CONFIG_PPC_WATCHDOG is enabled, we always cap the decrementer to
0x7fffffff. As suggested by Nick, add a run time check of the watchdog
cpumask, so if it is disabled we use the large decrementer.
Signed-off-by: Anton Blanchard <anton@samba.org>
---
arch/powerpc/kernel/time.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c
index 6a1f0a084ca3..3372019f52bd 100644
--- a/arch/powerpc/kernel/time.c
+++ b/arch/powerpc/kernel/time.c
@@ -60,6 +60,7 @@
#include <linux/rtc.h>
#include <linux/sched/cputime.h>
#include <linux/processor.h>
+#include <linux/nmi.h>
#include <asm/trace.h>
#include <asm/io.h>
@@ -575,7 +576,8 @@ void timer_interrupt(struct pt_regs *regs)
* 31 bits, which is about 4 seconds on most systems, which gives
* the watchdog a chance of catching timer interrupt hard lockups.
*/
- if (IS_ENABLED(CONFIG_PPC_WATCHDOG))
+ if (IS_ENABLED(CONFIG_PPC_WATCHDOG) &&
+ cpumask_test_cpu(smp_processor_id(), &watchdog_cpumask))
set_dec(0x7fffffff);
else
set_dec(decrementer_max);
--
2.17.1
next prev parent reply other threads:[~2018-09-29 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 1:26 [PATCH 1/2] powerpc/time: Use clockevents_register_device(), fixing an issue with large decrementer Anton Blanchard
2018-09-29 1:26 ` Anton Blanchard [this message]
2018-09-29 4:11 ` [PATCH 2/2] powerpc/time: Only cap decrementer when watchdog is enabled kbuild test robot
2018-09-29 5:16 ` Nicholas Piggin
2018-10-01 22:57 ` Anton Blanchard
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=20180929012607.10204-2-anton@ozlabs.org \
--to=anton@ozlabs.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oohall@gmail.com \
--cc=paulus@samba.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).