My current thought is that if more than (say) 100 consecutive attempts
to read the clocksource get hit with excessive delays, it is time to at
least do a WARN_ON(), and maybe also time to disable the clocksource
due to skew. The reason is that if reading the clocksource -always-
sees excessive delays, perhaps the clock driver or hardware is to blame.
Thoughts?