i386: Fix softirq accounting with 4K stacks
In-Reply-To: <[email protected]>
Quoted 2 lines · Bjorn Steinbrink
Btw, which path do apic irqs go? I stumbled across the nmi stuff, but didn't see anything special for the apic irqs.
arch/i386/kernel/entry.S has the macro BUILD_INTERRUPT(name, nr).
The code that uses this macro is in arch/i386/mach-*/entry_arch.h.
The macro prepends "smp_" to the name passed to the macro and the generated asm code calls that function after saving registers, etc.
arch/i386/kernel/apic.c::apic_intr_init() calls set_intr_gate() to point some of the interrupt gates at the correct functions.
Signature · 2 lines
Chuck "You can't read a newspaper if you can't read." --George W. Bush
Quoted 9 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
Quoted 2 lines · Bjorn Steinbrink
Btw, which path do apic irqs go? I stumbled across the nmi stuff, but didn't see anything special for the apic irqs.
arch/i386/kernel/entry.Shas the macroBUILD_INTERRUPT(name, nr).
Quoted 7 lines
The code that uses this macro is in
arch/i386/mach-*/entry_arch.h.The macro prepends "
smp_" to the name passed to the macro and the generated asm code calls that function after saving registers, etc.arch/i386/kernel/apic.c::apic_intr_init() calls
set_intr_gate()to point some of the interrupt gates at the correct functions.
Thanks, my view on the code was too cscope-centric and the grep runs searched for the full function name.
That finally explains why calling update_process_times() in smp_local_timer_interrupt() makes a difference on UP.
Björn