> Alternatively there is a sched_idle kernel patch, so you could
> start your X with it and it will only get the cycles *not* used
> by *any* other program.  Again, you see this can be ... strange.

Don't use that for the X server. Any program going into a tight loop
will deprive the X server of any CPU time, so you won't be able to do
_anything_ (besides logging in over the network or a serial port) when
this happens, and if you don't have the necessary equipment, need the
reset button.

Olaf

Reply via email to