16 Oct
2017
16 Oct
'17
12:08 p.m.
On 16/10/2017 10:11, Arnd Bergmann wrote:
Thanks!
Since you've looked at it overall, do you have an opinion on the question how to fix the PV interface to deal with the pvclock_wall_clock overflow?
It has to be done separately for each hypervisor.
In KVM, for example, it is probably best to abandon pvclock_read_wallclock altogether, and instead use the recently introduced KVM_HC_CLOCK_PAIRING hypercall. drivers/ptp/ptp_kvm.c is already using it and it's y2106 safe.
Paolo
Should we add a new version now and deprecate the existing one, or do you think that y2106 is far enough out that we should just ignore the problem?