On Fri, May 12, 2017 at 10:26:12AM -0700, John Stultz wrote: > On Fri, May 12, 2017 at 8:14 AM, Miroslav Lichvar <[email protected]> wrote: > > I see this with real PHCs and PTP/NTP synchronization too. It's very > > confusing when the timekeeping changes so much for no apparent reason. > > If we can't remove the old vsyscalls yet, I was thinking maybe a new > > flag could be added to adjtimex to report the error, so applications > > can at least detect this problem and consider stepping the clock in > > order to reset the error? > > > > Thoughts? > > I'd rather not have short-term hacks that applications have to adapt. > So I think we should drop the old vsyscall method in the near term. > Sorry this sort of fell off my radar.
Ok. Sounds good. > Do you have an updated set of patches you want to get ready to address > the issue? We can get those reviewed while we increase the pressure on > dropping the OLD_VSYSCALL implementations. I'll send an RFC series shortly. Thanks, -- Miroslav Lichvar
