Re: [RFC] Improved add_timer_randomness for __CRIS__ (instead of rdtsc())

> > > Perhaps something like:
> > > 
> > > speed=get_timestamp_khz;
> > > lowbits=get_hires_timestamp();
> > 
> > But isn't the "num ^= high;" a way to improve the randomness
> > and the high value doesn't really need to be linear to the time?
> 
> No, the high order bits aren't very interesting at all. Don't worry
> about that bit, it's just cuteness.

ok:-)
But if the the timestamp doesn't have to be entirely accurate
the name should perhaps reflect that, since at least on the cris arch
you can save some cycles if you can accept a glitch now and then.
We want to be able to separate it from similar functions used
for high-res timers etc. which need a more accurate function.

/Johan