>> What happens when adjtimex is not present? >> Is there no kernel space function for that? >> Does this patch affect "not setting correct time on restore" or "not setting >> correct time on live migration" bug? >> > > If adjtimex is not present, then the slew time part didn't take effect. > There is a kernel space do_adjtmex, but it's only for sys call and not exposed to module. So I didn't use it in my patch. > With this patch, it will step the clock if the time drift is larger than 1 seconds, so it can solve > the issue your mentioned. And on the other hand, "setting correct time on restore" is already fixed > in other patch, which is already in upstream. > AFAIK CENTOS and RHEL stopped providing adjtimex for a while now (since V5?). Even went as far as removing references from there man page for hwclock. in V6 On CENTOS 6.5 yum provides */adjtimex Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile * base: centosc6.centos.org * extras: centosb5.centos.org * updates: centosb6.centos.org No Matches found So the end user will have to go searching the internet rpmfind or something to install an unofficial package on an enterprise product. So by default you will be stepping time on CENTOS/RHEL 6 and above: with the result of an unstable clock. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
