If this function is called every 100ms, as you previously wrote, then you get 10 jiffies per call. Shouldn't it be 1 jiffy per 100ms? Shouldn't you multiply by 10 instead?
I guess your calculation is right, but I can't figure it out.
Date: Fri, 3 Sep 2010 00:42:47 +0200 From: firstname.lastname@example.org To: email@example.com CC: firstname.lastname@example.org Subject: Re: [coLinux-users] Very large time offset in coLinux
we don't use RDTSC directly. We use windows API, and that should
work without problems. KeQueryPerformanceCounter is the only
function with smallest time interval. Of curse I also have seen
updates for broken KeQueryPerformanceCounter:
The problem is not to follow the time. If the timediff is more as
one second, for example if you suspend Windows, then we set the time
absolutely. The problem is, from where we can get the exact time
stamp, if KeQueryPerformanceCounter is wrong?