Re: hires timer patchset [was Re: 2.6.19 -mm merge plans]

[Voluspa]

On Sat, 23 Sep 2006 22:20:27 +0200 Ingo Molnar wrote:
> 
> * Voluspa wrote:
> 
> > WARNING: "monotonic_clock" [drivers/char/hangcheck-timer.ko]
> > undefined!
> 
> turn off the CONFIG_HANGCHECK_TIMER option.
> 
> > WARNING: "hrtimer_stop_sched_tick" [drivers/acpi/processor.ko]
> > undefined! WARNING:
> > "hrtimer_restart_sched_tick" [drivers/acpi/processor.ko] undefined!
> 
> add these two lins to the end of kernel/hrtimer.c:
> 
> EXPORT_SYMBOL_GPL(hrtimer_stop_sched_tick);
> EXPORT_SYMBOL_GPL(hrtimer_restart_sched_tick);

My mind was clouded close to bedtime. I now remember the fix that
was published already at 2.6.17 time, from Steven Rostedt:

http://marc.theaimsgroup.com/?l=linux-kernel&m=115124086410874&w=2

Well, result is that NO_HZ indeed is the culprit for this CPU
issue. /proc/interrupts showed the timer to be stuck on an initial 3044
triggers after boot, while NMI: counted up almost as fast as LOC: (if
that tells any tale). Observing "top -d 1" for awhile revealed SYS
bursting (almost regularly alternating) between 50% and 100% CPU each 2
to 3 seconds. In between it was 0. USER also had the same pattern, but
with much longer duration. Perhaps 10 seconds from one show to the next.

I've gotten the broken out hrt-dyntick1 patches so will be able to
experiment on my own - slowly, on spare time.

I am of course available for any thoughts or trials you can come up
with in the meantime.

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