diff options
author | Paul E. McKenney <paulmck@kernel.org> | 2021-05-27 12:01:20 -0700 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2021-06-22 16:53:16 +0200 |
commit | 7560c02bdffb7c52d1457fa551b9e745d4b9e754 (patch) | |
tree | 8abaac4ea4ec95b5ecd4ea3768b3dd722a926218 /scripts/kernel-doc | |
parent | db3a34e17433de2390eb80d436970edcebd0ca3e (diff) | |
download | linux-7560c02bdffb7c52d1457fa551b9e745d4b9e754.tar.bz2 |
clocksource: Check per-CPU clock synchronization when marked unstable
Some sorts of per-CPU clock sources have a history of going out of
synchronization with each other. However, this problem has purportedy been
solved in the past ten years. Except that it is all too possible that the
problem has instead simply been made less likely, which might mean that
some of the occasional "Marking clocksource 'tsc' as unstable" messages
might be due to desynchronization. How would anyone know?
Therefore apply CPU-to-CPU synchronization checking to newly unstable
clocksource that are marked with the new CLOCK_SOURCE_VERIFY_PERCPU flag.
Lists of desynchronized CPUs are printed, with the caveat that if it
is the reporting CPU that is itself desynchronized, it will appear that
all the other clocks are wrong. Just like in real life.
Reported-by: Chris Mason <clm@fb.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Feng Tang <feng.tang@intel.com>
Link: https://lore.kernel.org/r/20210527190124.440372-2-paulmck@kernel.org
Diffstat (limited to 'scripts/kernel-doc')
0 files changed, 0 insertions, 0 deletions