* Matt Mackall <mpm@selenic.com> wrote:

quoted text
> > question is if it's significantly worse than before. With a 100 or 
> > 1000Hz timer, you can't expect perfect fairness just due to the 
> > extremely rough measurement of time spent...
> 
> Indeed. I'm just pointing out that not having TSC, fast HZ, no-HZ 
> mode, or high-res timers should not be treated as an unusual 
> circumstance. That's a PC-centric view.

actually, you dont need high-res or fast HZ or TSC to reduce those timer 
artifacts: all you need is _two_ (low-res, slow) hw clocks.

Most platforms do have that (even the really really cheap ones), but 
arches do not set up the scheduler tick one of them and the timer tick 
to the other, and to skew the periodic-timer programming setup a bit (by 
nature of physics they are usually already skewed a bit) so that the 
scheduler tick and timer tick are not coupled. This whole thing is not a 
big deal on embedded anyway. (you dont get students log in to the 
toaster or to the fridge to run timer exploits, do you? :-)

	Ingo
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/