RE: nmi_watchdog fix for x86_64 to be more like i386

From: Pallipadi, Venkatesh
Date: Fri Oct 05 2007 - 14:29:22 EST




>-----Original Message-----
>From: linux-kernel-owner@xxxxxxxxxxxxxxx
>[mailto:linux-kernel-owner@xxxxxxxxxxxxxxx] On Behalf Of
>Thomas Gleixner
>Sent: Monday, October 01, 2007 11:19 PM
>To: Andi Kleen
>Cc: Arjan van de Ven; David Bahi; LKML;
>linux-rt-users@xxxxxxxxxxxxxxx; Andrew Morton; Ingo Molnar;
>Gregory Haskins
>Subject: Re: nmi_watchdog fix for x86_64 to be more like i386
>
>>
>> The only workaround for chipsets ignoring IRQ affinity would
>be to keep
>> track on which CPU irq 0 happens and then restart APIC timer
>interrupts
>> on the others (or send IPIs) as needed. But that would be
>fairly ugly.
>
>The clock events code does handle this already. The broadcast
>interrupt
>can come in on any cpu. It's just the nmi watchdog which would
>be affected
>by that.
>

Probably we can workaround this by keeping track of IRQ0 count at percpu
level and
use local apic timer + this percpu counter in NMI. Or just increment
local
apic timer count in IRQ0 with nohz enabled.

Thanks,
Venki
-
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/