How to stop time from running backwards on Linux?

Question

Here's a little test I've written to verify that time does indeed only run forwards in Linux.

#include <time.h>
#include <sys/time.h>  

bool timeGoesForwardTest2()
{
   timeval tv1, tv2;   
   double startTime = getTimeSeconds();  // my function

   while ( getTimeSeconds() - startTime < 5 )
   {
      gettimeofday( &tv1, NULL );  
      gettimeofday( &tv2, NULL );  

      if ( tv2.tv_usec == tv1.tv_usec &&
           tv2.tv_sec == tv1.tv_sec )
      {
         continue;  // Equal times are allowed.
      }

      // tv2 should be greater than tv1
      if ( !( tv2.tv_usec>tv1.tv_usec ||
              tv2.tv_sec-1 == tv1.tv_sec ) )
      {
         printf( "tv1: %d %d\n", int( tv1.tv_sec ), int( tv1.tv_usec ) );
         printf( "tv2: %d %d\n", int( tv2.tv_sec ), int( tv2.tv_usec ) );
         return false;
      }         
   }
   return true;
}

Test fails with the result.

 tv1: 1296011067 632550
 tv2: 1296011067 632549

ummm....

Why does this happen?

Here's my setup:

Linux version 2.6.35-22-generic (buildd@rothera) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4) ) #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 (Ubuntu 2.6.35-22.33-generic 2.6.35.4)
... running inside VirtualBox 3.2.12, in Windows 7.

It may have to do with the VM. Have you tried doing this with an actual Linux install? — Rafe Kettler, Jan 26 '11 at 03:13
Make sure you are checking for integer rollover on tv_sec and tv_usec whenever doing any calculations with them. — Will Tate, Jan 26 '11 at 03:17
I suspect it's because the time calls go out to two different cores on your CPU and one of them is in the vicinity of a miniature black hole. Get out of the house. As quick as you can. Seriously! — paxdiablo, Jan 26 '11 at 03:19
The bottom-left panel of http://xkcd.com/821/ comes to mind. — Maxpm, Jan 26 '11 at 03:22
@paxdiablo - Looks like someone's coding for the Large Hadron Collider. — Chris Lutz, Jan 26 '11 at 05:59
Since gettimeofday has been removed in POSIX.1-2008, might as well use clock_gettime, also because it provides nsec granularity. (And not just because of the monotonicity option.) — user562374, Jan 26 '11 at 09:33
Your clock might be running backwards but hopefully time itself is unaffected by your choice of operating system. — Noel Walters, Feb 01 '11 at 11:57
Try spinning your little spinning top thing, see if it falls over. — Phil H, Jun 20 '12 at 14:33

score 30 · Answer 1 · answered Jan 26 '11 at 03:20

30

gettimeofday() is not guaranteed to be monotonic. Use clock_gettime(CLOCK_MONOTONIC) if you need that guarantee.

answered Jan 26 '11 at 03:20

ephemient

198,619
38
280
391

This is true, but the bugtracker link posted by @vz0 says that the same issue occurs under VirtualBox with `CLOCK_MONOTONIC`, so there is also a bug here. – caf Jan 26 '11 at 09:10

score 17 · Accepted Answer · answered Jan 26 '11 at 03:25

17

There is an open issue at the VirtualBox Bug Tracker. They link to a blog post stating why you shouldn't use gettimeofday() to measure the passage of time:

The most portable way to measure time correctly seems to be clock_gettime(CLOCK_MONOTONIC, ...)

answered Jan 26 '11 at 03:25

vz0

32,345
7
44
77

1

The bugtracker link also points out that `CLOCK_MONOTONIC` exhibits the same problem - as does FreeBSD running under VirtualBox. It appears to be a VirtualBox bug. – caf Jan 26 '11 at 09:09
Time on VMs seems to be pretty fruity anyway. My VMWare install at work suddenly decided it was going to tick time at 1/2 the correct rate. – Paul Nathan Jan 26 '11 at 15:37
This seems to be right. gettimeofday is problematic for me on native and virtual machines. clock_gettime however also seems to fail for VirtualBox. Bug is in VirtualBox. – user48956 Jan 26 '11 at 19:25
It's a Linux kernel bug. **None** of the linux kernel timers seem to work right in a VM, because of the enormous effort they go to to avoid using the BIOS calls for the current time, which the VM answers to. – Ben Apr 15 '11 at 16:10

score 10 · Answer 3 · answered Jan 26 '11 at 03:17

10

Machine timers on most machines only have about 15 usec precision (even to native code). Time going 'backward' is odd, but you really can't rely on that level (1 usec) anyway. (Also note: there is a difference between precision and accuracy; the accuracy of most timers is worse than its precision). The use of a virtual machine may aggravate this as well.

Update: Typo

answered Jan 26 '11 at 03:17

phooji

10,086
2
38
45

Great point about precision versus accuracy. Case in point: RDTSC has extreme precision (sub-nanosecond on many modern machines) yet potentially much worse accuracy than any normal timekeeping functions. – ephemient Jan 26 '11 at 05:28

Paul Sasik · Answer 4 · 2011-01-26T05:55:11.160

5

It's not that it's running backwards. It'd be better to say that it is not reporting the correct time. This is because computers, without the aid of a dedicated timing subsystem, simply are not capable of reporting time very accurately in single millisecond intervals.

The precision will vary with hardware, the OS and even the power supply. Here is an article for starters. A bit old but communicates the idea nicely.

edited Jan 26 '11 at 05:55

answered Jan 26 '11 at 03:16

Paul Sasik

79,492
20
149
189

This answer is nonsense. Any modern Unix-like system will give precision to 10 millisecond resolution or better, and nanosecond resolution is not uncommon. I hear Windows doesn't do a bad job either... – R.. GitHub STOP HELPING ICE Jan 26 '11 at 05:28
@R: I was thinking along the lines of old Windows interrupt timers when i quoted the original resolution. Updated my answer for modern times... – Paul Sasik Jan 26 '11 at 05:59

score 1 · Answer 5 · answered Jan 26 '11 at 11:34

Time should not run backwards on real hardware; on a VM your mileage may vary.

In any case, your application should probably not assume that time doesn't run backwards by a very small amount (think, maybe 1 second).

Yes, clock_gettime is good but even that could run backwards in the case of faulty hardware (or a VM, as in your example).

I have seen a hardware bug make time run backwards (albeit very occasionally), it was a cause of some very peculiar problems.

In particular, anything which involves comparing file timestamps will go wrong when time goes backwards.

How to stop time from running backwards on Linux?

5 Answers5

Linked