From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Joe Korty <joe.korty@ccur.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sven-Thorsten Dietrich <sdietrich@novell.com>,
"H. Peter Anvin" <hpa@zytor.com>,
mingo@elte.hu, tglx@linutronix.de,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
jason.baietto@ccur.com
Subject: Re: [PATCH] expand /proc/interrupts to include missing vectors, v2
Date: Wed, 1 Aug 2007 09:29:04 -0400 [thread overview]
Message-ID: <20070801132904.GA14084@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20070731001718.GA14295@tsunami.ccur.com>
On Mon, Jul 30, 2007 at 08:17:18PM -0400, Joe Korty wrote:
> Add missing IRQs and IRQ descriptions to /proc/interrupts.
>
> /proc/interrupts is most useful when it displays every
> IRQ vector in use by the system, not just those somebody
> thought would be interesting.
>
> This patch inserts the following vector displays to the
> i386 and x86_64 platforms, as appropriate:
>
> rescheduling interrupts
> TLB flush interrupts
> function call interrupts
> thermal event interrupts
> threshold interrupts
> spurious interrupts
>
> A threshold interrupt occurs when ECC memory correction
> is occuring at too high a frequency. Thresholds are used
> by the ECC hardware as occasional ECC failures are part
> of normal operation, but long sequences of ECC failures
> usually indicate a memory chip that is about to fail.
>
> Thermal event interrupts occur when a temperature threshold
> has been exceeded for some CPU chip. IIRC, a thermal
> interrupt is also generated when the temperature drops
> back to a normal level.
>
> A spurious interrupt is an interrupt that was raised then
> lowered by the device before it could be fully processed
> by the APIC. Hence the apic sees the interrupt but does
> not know what device it came from. For this case the APIC
> hardware will assume a vector of 0xff.
>
> Rescheduling, call, and TLB flush interrupts are sent from
> one CPU to another per the needs of the OS. Typically,
> their statistics would be used to discover if an
> interrupt flood of the given type has been occuring.
Since you are playing with /proc/interrupts, is there any chance you
could make it make sense too?
Right now I have the annoying issue that /proc/interrupts only shows
interrupts that it sees a handler for, and ignores the rest. For some
reason irq 3 never shows up in /proc/interrupts on my system, even
though I have serial ports on both IRQ 3 and 4. Only irq 4 shows
'serial' as the handler, and is the only one shown. irq 3 is getting
lots of interrupts, and the serial driver is handling them, it just
doesn't show up in /proc/interrupts. procinfo does show irq 3 although
with no handler listed. I think any interrupt with a handler AND any
interrupt with a non zero count ought to be shown. I only happened to
try procinfo by chance and discover that while I thought IRQ 3 wasn't
working, the only issue was that /proc/interrupts simply wasn't showing
all the relevant information.
Of course I would also love to know why irq 3 isn't showing serial as
the handler, but I have no idea why that is. This is all using Debian's
2.6.18 kernel.
--
Len Sorensen
prev parent reply other threads:[~2007-08-01 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 18:05 [PATCH] create /proc/all-interrupts Joe Korty
2007-07-26 18:56 ` H. Peter Anvin
2007-07-30 17:33 ` Sven-Thorsten Dietrich
2007-07-30 19:32 ` Andrew Morton
2007-07-30 19:42 ` Joe Korty
2007-07-31 0:17 ` [PATCH] expand /proc/interrupts to include missing vectors, v2 Joe Korty
2007-07-31 0:48 ` Gabriel C
2007-07-31 1:48 ` Andrew Morton
2007-07-31 14:19 ` [PATCH] expand /proc/interrupts to include missing vectors, v3 Joe Korty
2007-07-31 17:02 ` Andi Kleen
2007-07-31 20:29 ` Joe Korty
2007-07-31 21:06 ` [PATCH] expand /proc/interrupts to include missing vectors, v4 Joe Korty
2007-08-01 13:29 ` Lennart Sorensen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070801132904.GA14084@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jason.baietto@ccur.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®