* Daniel Walker <dwalker@mvista.com> wrote:

quoted text
> > > > the kernel simply displays reality: IRQ#0 isnt increasing 
> > > > because it's not used, and LOC (local apic timers) is 
> > > > increasing.
> > > 
> > > What about the statistics for the other interrupts in the system ? 
> > > It clearly doesn't list all interrupts in the system .
> > 
> > what is your point?
> 
> Isn't the listing inconsistent ? /proc/interrupts only showing some 
> special interrupts, and not others .. For example it shows NMI which 
> is not related to request_irq() .. It shows some clock driver devices 
> (timer, NMI, LOC) and not others (clock event devices) ..

it's not inconsistent. /proc/interrupts lists registered interrupts plus 
some special hardcoded platform interrupts that are not explicitly 
registered - with the goal of providing a list of all active interrupt 
sources. /proc/interrupts has been doing that for more than 10 years. 
Clock event devices themselves are not 'interrupt lines', why should 
they be listed in /proc/interrupts?

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