dtrace users opinion solicited (timestamps)
Andriy Gapon
avg at freebsd.org
Fri Jul 10 05:50:52 UTC 2009
on 10/07/2009 05:54 Tim Kientzle said the following:
>
> Instead of just storing tsc_freq at each frequency change,
> you really need:
> * Last timestamp just before frequency change (t0)
> * new frequency (f)
> * TSC value at frequency change (c0)
>
> Then
> t = t0 + (rdtsc() - c0) / f
>
> Of course, I haven't looked at the code to tell
> what your range limitations are.
Yes, tracking the TSC frequency changes should allow us to have correct DTrace
timecounting. But I am not sure if we really need this (or can have this).
Because otherwise I can not see why we have a distinct/specialized DTrace
TSC-based timecounting when we already have general purpose TSC timecounting
that already works correctly (if I am not mistaken).
--
Andriy Gapon
More information about the freebsd-current
mailing list