* Con Kolivas [050901 08:22]: > On Thu, 1 Sep 2005 02:58 am, Srivatsa Vaddagiri wrote: > > Following patches related to dynamic tick are posted in separate mails, > > for convenience of review. The first patch probably applies w/o dynamic > > tick consideration also. > > > > Patch 1/3 -> Fixup lost tick calculation in timer_pm.c > > Patch 2/3 -> Dyn-tick cleanups > > Patch 3/3 -> Use lost tick information in dyn-tick time recovery > > > > These patches are against 2.6.13-rc6-mm2. > > > > Con, would be great if you can upload a consolidated new version of > > dyn-tick patch on your website! > > Great, thanks. I'll wait till 2.6.13-mm1 is out since that's due shortly and > I'll resync everything with that and perhaps tweak along the way. I tried this quickly on a loaner ThinkPad T30, and needed the following patch to compile. The patch does work with PIT, but with lapic the system does not wake to timer interrupts :( I also hacked together a little timer test utility that should go trough on a completely idle system with no errors. Also posted it to: http://www.muru.com/linux/dyntick/tools/dyntick-test.c Srivatsa, could you try the dyntick-test.c on your system after booting to init=/bin/sh to make the system as idle as possible? Unfortunately I cannot debug the APIC issue right now, but I seem to have an issue on ARM OMAP where the timer test occasionally fails on some longer values, for example 3 second sleep can take 4 seconds. I don't know yet if this is the problem George Anzinger mentioned with next_timer_interrupt(), or if this is OMAP specific. But it only seems to occur with very low idle HZ values. This may be related to the slow boot time issue I mentioned yesterday. Regards, Tony