From: "Paul E. McKenney" <paulmck@kernel.org>
To: 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
Subject: [PATCH clocksource 0/2] Clocksource-watchdog classification and backoff
Date: Wed, 2 Nov 2022 11:40:01 -0700 [thread overview]
Message-ID: <20221102184001.GA1306489@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello!
This series adds comments classifying bogus measurements and adds capped
exponential backoff for messages that are likely caused by overly busy
systems.
1. Add comments to classify bogus measurements.
2. Exponential backoff for load-induced bogus watchdog reads.
Thanx, Paul
------------------------------------------------------------------------
b/include/linux/clocksource.h | 4 ++++
b/kernel/time/clocksource.c | 2 ++
kernel/time/clocksource.c | 31 +++++++++++++++++++++++++------
3 files changed, 31 insertions(+), 6 deletions(-)
next reply other threads:[~2022-11-02 18:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 18:40 Paul E. McKenney [this message]
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
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=20221102184001.GA1306489@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--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=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=neeraju@codeaurora.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®