On Sun, Jun 7, 2020 at 11:36 AM Thomas Gleixner wrote:
>
> Miklos reported [1] that the recent VDSO changes broke paravirt clocksource
> based VDSO in the case that the clocksource is invalidated by the
> hypervisor which happens after a suspend/resume cycle of the host.
>
> The result is a stale
Miklos reported [1] that the recent VDSO changes broke paravirt clocksource
based VDSO in the case that the clocksource is invalidated by the
hypervisor which happens after a suspend/resume cycle of the host.
The result is a stale clocksource which is about 2200 seconds ahead of the
actual time
2 matches
Mail list logo
