Re: [patch] clockevents: drivers for i386, fix #2

[Thomas Gleixner]

On Wed, 2006-10-04 at 12:53 +0200, Ingo Molnar wrote:
> there's one material difference we just found: in the !hres case we'll 
> do the timer IRQ handling mostly from the lapic vector - while in 
> mainline we do it from the irq0 vector. So, how does your 
> /proc/interrupts look like? How frequently does LOC increase, and how 
> frequently does IRQ 0 increase?
> 
> (meanwhile we'll fix and restore things so that it matches mainline 
> behavior.)

Andrew, does the patch below fix your problem ?

You should see the same weird behaviour when you run a plain -mm3 with
CONFIG_SMP=y on that box. This moves update_process_times() to the lapic
too.
	tglx


Index: linux-2.6.18-mm3/arch/i386/kernel/apic.c
===================================================================
--- linux-2.6.18-mm3.orig/arch/i386/kernel/apic.c	2006-10-04 13:02:35.000000000 +0200
+++ linux-2.6.18-mm3/arch/i386/kernel/apic.c	2006-10-04 12:59:06.000000000 +0200
@@ -84,7 +84,9 @@ static void lapic_timer_setup(enum clock
 static struct clock_event_device lapic_clockevent = {
 	.name = "lapic",
 	.capabilities = CLOCK_CAP_NEXTEVT | CLOCK_CAP_PROFILE
+#ifdef CONFIG_SMP
 			| CLOCK_CAP_UPDATE,
+#endif
 	.shift = 32,
 	.set_mode = lapic_timer_setup,
 	.set_next_event = lapic_next_event,




-
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/