dtrace users opinion solicited (timestamps)

[Thomas Backman]

On Jul 9, 2009, at 19:31, Andriy Gapon wrote:
> There are at least the following two alternatives:
>
> 1. Keep things as they are and warn users not to change CPU clock  
> frequency when
> they use DTrace and the CPU doesn't have invariant TSC. I think that  
> this should
> cause only minor inconveniences to a portion of DTrace users.
Hmm, but "things as they are" causes an overflow about every 10  
seconds, so the value is quite useless now (which, of course, you know  
about, having written a patch for it :)
Is scenario #1 after the patch (PR kern/127441 for the rest of you) or  
not?

Regards,
Thomas