On 07/24/2012 07:40 PM, Paul E. McKenney wrote: > The interrupt flag is zero, so interrupts are disabled. So my question > to you is "Why did do_pageattr_test() or one of the functions it called > disable interrupts for more than one hundred thousand jiffies?" > > I can't see where it is disabling interrupts, but the EFLAGS register > above does indicate that they are disabled. Or is this something useless > that is just telling us that receiving the NMI disabled interrupts?
Doesn't the stack of CPU1 show that it's currently handling an interrupt: [ 215.026612] Call Trace: [ 215.026612] <IRQ> [ 215.026612] [<ffffffff81095d07>] native_apic_msr_eoi_write+0x27/0x30 [ 215.026612] [<ffffffff810901c4>] smp_apic_timer_interrupt+0x34/0xa0 [ 215.026612] [<ffffffff8369c4af>] apic_timer_interrupt+0x6f/0x80 [ 215.026612] <EOI> Or am I reading that wrong? In that case, it had nothing to do with pageattr which just happened to be on the stack at that time. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
