* Daniel Walker <[email protected]> wrote:
> > we could make this clearer by renaming 'LOC' (which stands for
> > 'LOCal timer interupts' and was added [and misnamed] by yours truly
> > many moons ago) to 'apic-timer' and 'timer' to 'PIT-timer' but
> > /that/ would be more of a userspace visible change than the change
> > in the counter rates.
>
> If we change the current "timer" entry to be listed as "lapic-timer"
> and not "IO-APIC-edge" (or one of the other names) and replace it with
> the count from LOC , [...]
doing that would not fake the old behavior (which is your suggestion),
LOC is per CPU, while the PIT timer irq that was there is global.
But, as per the previous mails, the new behavior is just fine, because
/proc/interrupts just reflects reality. And the way the kernel utilizes
the hardware has just changed - for the better.
The same happens when say a network driver implements NAPI: the IRQ
count goes way, way down. Or if a driver starts supporing MSI - the IRQ
line even moves to another one. Do we try to fix those counts up to
match the 'previous behavior'? Of course not. What you are suggesting
makes no sense, is against current kernel practices - as we pointed it
out to you 7 mails ago.
> [...] that would make sense cause that field already changes depending
> if you have a io-apic or not ..
(that is something else: it's different because a different irq-chip is
behind it.)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
