On Wed, Apr 16 2025 at 22:29, John Stultz wrote:
Looking over the patch, it seems ok to me, but in a test run with it, I've seen an error with CLOCK_REALTIME_COARSE during the clocksource-switch test (as well as some seemingly unrelated test errors, which I need to investigate) so I'm looking at the zeroing done in timekeeping_forward_now and will try to look more into this tomorrow.
Odd. I ran all the test nonsense here and did not run into any issues.