summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2022-12-07 06:36:10 +0300
committerPaul E. McKenney <paulmck@kernel.org>2023-01-04 07:43:45 +0300
commitc37e85c135cead4256dc8860073c468d8925c3df (patch)
treed7871da13c5a39e5adff5a455935260f5502c48a /tools/perf/scripts/python/exported-sql-viewer.py
parentbeaa1ffe551c330d8ea23de158432ecaad6c0410 (diff)
downloadlinux-c37e85c135cead4256dc8860073c468d8925c3df.tar.xz
clocksource: Loosen clocksource watchdog constraints
Currently, MAX_SKEW_USEC is set to 100 microseconds, which has worked reasonably well. However, NTP is willing to tolerate 500 microseconds of skew per second, and a clocksource that is good enough for NTP should be good enough for the clocksource watchdog. The watchdog's skew is controlled by MAX_SKEW_USEC and the CLOCKSOURCE_WATCHDOG_MAX_SKEW_US Kconfig option. However, these values are doubled before being associated with a clocksource's ->uncertainty_margin, and the ->uncertainty_margin values of the pair of clocksource's being compared are summed before checking against the skew. Therefore, set both MAX_SKEW_USEC and the default for the CLOCKSOURCE_WATCHDOG_MAX_SKEW_US Kconfig option to 125 microseconds of skew per second, resulting in 500 microseconds of skew per second in the clocksource watchdog's skew comparison. Suggested-by Rik van Riel <riel@surriel.com> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions