From: "Paul E. McKenney" <paulmck@kernel.org>
To: tglx@linutronix.de
Cc: longman@redhat.com, feng.tang@intel.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL clocksource] Clocksource watchdog commits for v5.17
Date: Tue, 4 Jan 2022 16:17:23 -0800 [thread overview]
Message-ID: <20220105001723.GA536708@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello, Thomas,
This pull request contains a pair of changes, both courtesy of Waiman
Long:
1. Avoids accidental unstable marking of clocksources by rejecting
clocksource measurements where the source of the skew is the delay
reading reference clocksource itself. This change avoids many
of the current false positives caused by epic cache-thrashing
workloads.
https://lore.kernel.org/lkml/20211118191439.1000012-2-longman@redhat.com/
2. Reduces the default clocksource_watchdog() retries to 2, thus
offsetting the increased overhead due to #1 above rereading the
reference clocksource.
https://lore.kernel.org/lkml/20211118191439.1000012-3-longman@redhat.com/
These have been subjected to the kbuild test robot and -next testing,
and are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git clocksource
for you to fetch changes up to 1a5620671a1b6fd9cc08761677d050f1702f910c:
clocksource: Reduce the default clocksource_watchdog() retries to 2 (2021-11-30 17:22:29 -0800)
----------------------------------------------------------------
Waiman Long (2):
clocksource: Avoid accidental unstable marking of clocksources
clocksource: Reduce the default clocksource_watchdog() retries to 2
Documentation/admin-guide/kernel-parameters.txt | 4 +-
kernel/time/clocksource.c | 52 ++++++++++++++++++++-----
2 files changed, 44 insertions(+), 12 deletions(-)
next reply other threads:[~2022-01-05 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 0:17 Paul E. McKenney [this message]
2022-01-10 13:06 ` [tip: timers/core] Merge branch 'clocksource' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into timers/core tip-bot2 for Thomas Gleixner
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=20220105001723.GA536708@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=tglx@linutronix.de \
/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®