From: "Paul E. McKenney" <paulmck@kernel.org>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
john.stultz@linaro.org, ak@linux.intel.com,
rong.a.chen@intel.com, sboyd@kernel.org, longman@redhat.com
Subject: [GIT PULL clocksource] Clocksource watchdog commits for v5.18
Date: Wed, 23 Feb 2022 16:07:18 -0800 [thread overview]
Message-ID: <20220224000718.GA3747431@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello, Thomas,
This pull request contains a single change that allows build-time
adjustment of the clocksource watchdog maximum skew. The default remains
100 microseconds, but a new CLOCKSOURCE_WATCHDOG_MAX_SKEW_US Kconfig
option allows kernels to be built with this skew set in a range from
50 to 100 microseconds. This Kconfig option depends on the existing
CLOCKSOURCE_WATCHDOG option. This change has been posted to LKML:
https://lore.kernel.org/lkml/20211206033815.871823-1-longman@redhat.com/
this has 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.2022.02.01b
for you to fetch changes up to fc153c1c58cb8c3bb3b443b4d7dc3211ff5f65fc:
clocksource: Add a Kconfig option for WATCHDOG_MAX_SKEW (2022-02-01 17:35:43 -0800)
Please note that this is based on this mainline commit:
da123016ca8c ("rcu-tasks: Fix computation of CPU-to-list shift counts")
which is in turn based on v5.17-rc1.
----------------------------------------------------------------
Waiman Long (1):
clocksource: Add a Kconfig option for WATCHDOG_MAX_SKEW
kernel/time/Kconfig | 9 +++++++++
kernel/time/clocksource.c | 8 +++++++-
2 files changed, 16 insertions(+), 1 deletion(-)
next reply other threads:[~2022-02-24 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 0:07 Paul E. McKenney [this message]
2022-03-07 18:22 ` [tip: timers/core] Merge branch 'clocksource.2022.02.01b' 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=20220224000718.GA3747431@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=ak@linux.intel.com \
--cc=john.stultz@linaro.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=rong.a.chen@intel.com \
--cc=sboyd@kernel.org \
--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®