From: Waiman Long <longman@redhat.com>
To: "Paul E. McKenney" <paulmck@kernel.org>, tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, john.stultz@linaro.org,
sboyd@kernel.org, corbet@lwn.net, Mark.Rutland@arm.com,
maz@kernel.org, kernel-team@meta.com, neeraju@codeaurora.org,
ak@linux.intel.com, feng.tang@intel.com, zhengjun.xing@intel.com,
John Stultz <jstultz@google.com>
Subject: Re: [PATCH clocksource 1/2] clocksource: Add comments to classify bogus measurements
Date: Wed, 2 Nov 2022 22:23:25 -0400 [thread overview]
Message-ID: <7339298b-1156-2d24-7dd9-e7fae690773c@redhat.com> (raw)
In-Reply-To: <20221102184009.1306751-1-paulmck@kernel.org>
On 11/2/22 14:40, Paul E. McKenney wrote:
> An extremely busy system can delay the clocksource watchdog, so that
> the corresponding too-long bogus-measurement error does not necessarily
> imply an error in the system. However, a too-short bogus-measurement
> error likely indicates a bug in hardware, firmware or software.
>
> Therefore, add comments clarifying these bogus-measurement pr_warn()s.
>
> Reported-by: Feng Tang <feng.tang@intel.com>
> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> Cc: John Stultz <jstultz@google.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Cc: Feng Tang <feng.tang@intel.com>
> Cc: Waiman Long <longman@redhat.com>
> ---
> kernel/time/clocksource.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/time/clocksource.c b/kernel/time/clocksource.c
> index dcaf38c062161..3f5317faf891f 100644
> --- a/kernel/time/clocksource.c
> +++ b/kernel/time/clocksource.c
> @@ -443,10 +443,12 @@ static void clocksource_watchdog(struct timer_list *unused)
> /* Check for bogus measurements. */
> wdi = jiffies_to_nsecs(WATCHDOG_INTERVAL);
> if (wd_nsec < (wdi >> 2)) {
> + /* This usually indicates broken timer code or hardware. */
> pr_warn("timekeeping watchdog on CPU%d: Watchdog clocksource '%s' advanced only %lld ns during %d-jiffy time interval, skipping watchdog check.\n", smp_processor_id(), watchdog->name, wd_nsec, WATCHDOG_INTERVAL);
> continue;
> }
> if (wd_nsec > (wdi << 2)) {
> + /* This can happen on busy systems, which can delay the watchdog. */
> pr_warn("timekeeping watchdog on CPU%d: Watchdog clocksource '%s' advanced an excessive %lld ns during %d-jiffy time interval, probable CPU overutilization, skipping watchdog check.\n", smp_processor_id(), watchdog->name, wd_nsec, WATCHDOG_INTERVAL);
> continue;
> }
Looks good.
Reviewed-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2022-11-03 2:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 18:40 [PATCH clocksource 0/2] Clocksource-watchdog classification and backoff Paul E. McKenney
2022-11-02 18:40 ` [PATCH clocksource 1/2] clocksource: Add comments to classify bogus measurements Paul E. McKenney
2022-11-03 2:23 ` Waiman Long [this message]
2022-11-03 20:47 ` Paul E. McKenney
2022-11-04 2:13 ` Feng Tang
2022-11-02 18:40 ` [PATCH clocksource 2/2] clocksource: Exponential backoff for load-induced bogus watchdog reads Paul E. McKenney
2022-11-03 2:28 ` Waiman Long
2022-11-03 20:49 ` Paul E. McKenney
2022-11-04 0:20 ` Waiman Long
2022-11-04 0:26 ` Paul E. McKenney
2022-11-04 1:01 ` Waiman Long
2022-11-04 2:23 ` Paul E. McKenney
2022-11-04 13:55 ` Waiman Long
2022-11-05 2:38 ` Paul E. McKenney
2022-11-05 2:49 ` Waiman Long
2022-11-05 19:31 ` Paul E. McKenney
2022-11-04 2:16 ` Feng Tang
2022-11-04 2:25 ` Paul E. McKenney
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=7339298b-1156-2d24-7dd9-e7fae690773c@redhat.com \
--to=longman@redhat.com \
--cc=Mark.Rutland@arm.com \
--cc=ak@linux.intel.com \
--cc=corbet@lwn.net \
--cc=feng.tang@intel.com \
--cc=john.stultz@linaro.org \
--cc=jstultz@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=neeraju@codeaurora.org \
--cc=paulmck@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhengjun.xing@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®