The below patch allows to set the HZ dynamically at boot time withcommand line parameter. HZ=1000 HZ=100 HZ=333 any other value just works(though certain value may cause more or less drift to the system timeadvance/decrease).

Is there any interest from the mainline developers to merge this into2.6? I'm getting requests for this feature being forward ported to2.6 (both for batch jobs and for the powersaved that can trim the hzdown to 80mhz). It should be up to the user to choose the HZ like it wasin 2.4-aa.

This patch is quite intrusive since many HZ visible to userspace have tobe converted to USER_HZ, and most important because HZ isn't availableat compile time anymore and every variable in function of HZ must beeither changed to be in function of USER_HZ or it must be initialized atruntime. The code has debugging code (optional at compile time) so thatI can guarantee that there cannot be any regression.

Technically this makes a lot of sense to me (well, you can guess why Iimplemented it in the first place), at least in archs where one cannotreprogram the timer chip in a performant way (to stop timer tickscompletely until the next posted timer). This is in production for yearsin SLES8 btw.