>> And following your argument that these apps have been silenty broken
>> since 1999, if there's no broken app out there, nobody will ever get the
>> instruction fault. If there's any app broken out there we probably like
> No. rdtsc is still usefull if you are clever and statistically filter
> out. Also rdtsc provides you number of cycles, so if you want to know
> how many cycles mov %eax,%ebx takes, you can do that even on
> speedstep. Anything that correlates rdtsc to real time is broken, however.
It's not correlating it to real time that's the problem. It's getting resceduled
inbetween calls that hurts. Take your example.
<- get rescheduled here
Broken. May even take negative "time".
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Aug 31 2002 - 22:00:17 EST