>The value for TICK_USEC is defined as ((1000000UL + USER_HZ/2) / USER_HZ). > In my box, it's 10000. OK got it thanks . Checked the algorithm OK by me. Of course you can only adjust clock by a tick (smallest resolution) so you could be flapping between 2 values so as you say NTP is preferred. However it may be good enough for some scenarios. _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
- [PATCH 2/2] hyperv: Implement Time Synchronization using h... Thomas Shao
- Re: [PATCH 2/2] hyperv: Implement Time Synchronizatio... Dan Carpenter
- RE: [PATCH 2/2] hyperv: Implement Time Synchroniz... Thomas Shao
- Re: [PATCH 2/2] hyperv: Implement Time Synchr... Dan Carpenter
- RE: [PATCH 2/2] hyperv: Implement Time Sy... Thomas Shao
- Re: [PATCH 2/2] hyperv: Implement Time Synchr... Mike Surcouf
- RE: [PATCH 2/2] hyperv: Implement Time Sy... Thomas Shao
- Re: [PATCH 2/2] hyperv: Implement Ti... Mike Surcouf
- Re: [PATCH 2/2] hyperv: Implement Time Sy... Richard Cochran
- Re: [PATCH 2/2] hyperv: Implement Time Synchroniz... Joe Perches
- Re: [PATCH 2/2] hyperv: Implement Time Synchronizatio... Richard Cochran
- RE: [PATCH 2/2] hyperv: Implement Time Synchroniz... Thomas Shao
- Re: [PATCH 2/2] hyperv: Implement Time Synchr... Richard Cochran
- RE: [PATCH 2/2] hyperv: Implement Time Sy... Thomas Shao
- Re: [PATCH 2/2] hyperv: Implement Time Synchr... Richard Cochran
- RE: [PATCH 2/2] hyperv: Implement Time Sy... Thomas Shao
- Re: [PATCH 2/2] hyperv: Implement Time Sy... Mike Surcouf
- Re: [PATCH 2/2] hyperv: Implement Ti... Richard Cochran