Re: [QUESTION] sched/clock: Potential timestamp jump due to inter-CPU counter skew?

[Marc Zyngier]

On Mon, 26 Oct 2026 08:27:30 +0000,
Zhan Xusheng <zhanxusheng1024@xxxxxxxxx> wrote:
> 
> On arm64 the system counter is meant to give all PEs a common view of
> time, and keeping the copies on separate dies in step is the
> implementation's job.  The kernel has no tolerance for skew.  The counter
> errata handled in arm_arch_timer.c (Freescale A-008585, HiSilicon
> 161010101, Cortex-A73 858921, Allwinner A64) are all reads on a single
> CPU returning a wrong value, worked around by reading twice; none of them
> is skew between CPUs.

Indeed. If the implementation cannot give any two arbitrary CPUs
anywhere in the system the exact same view of the counter, then this
implementation is broken, and unsupported. No discussion.

	M.

-- 
Without deviation from the norm, progress is not possible.