From: Len Brown <len.brown@intel.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6 /proc/interrupts fails on systems with many CPUs
Date: 11 Nov 2003 14:55:28 -0500 [thread overview]
Message-ID: <1068580528.26160.12.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0013B1188@hdsmsx402.hd.intel.com>
Speaking of /proc/interrupts...
Does anybody else find hw_interrupt_type.typename lacking?
"XT-PIC" doesn't tell us if it is level or edge triggered, high or low
polarity.
"IO-APIC-edge" and "IO-APIC-level" don't tell us if it is high or low
polarity.
Having this info easily available in /proc/interrupts would make
recognizing and diagnosing interrupt configuration issues much easier.
thanks,
-Len
next parent reply other threads:[~2003-11-11 19:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0013B1188@hdsmsx402.hd.intel.com>
2003-11-11 19:55 ` Len Brown [this message]
2003-11-11 23:37 ` 2.6 /proc/interrupts fails on systems with many CPUs Erlend Aasland
2003-11-12 2:35 ` Martin J. Bligh
2003-11-11 18:15 Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2003-11-11 17:21 Erik Jacobson
2003-11-11 17:29 ` Randy.Dunlap
2003-11-11 17:51 ` Robert Love
2003-11-11 18:02 ` Martin J. Bligh
2003-11-11 18:24 ` Linus Torvalds
2003-11-11 18:57 ` Martin J. Bligh
2003-11-11 18:36 ` Linus Torvalds
2003-11-11 20:14 ` Anton Blanchard
2003-11-11 22:41 ` Martin J. Bligh
2003-11-11 22:32 ` Zwane Mwaikambo
2003-11-11 18:17 ` Linus Torvalds
2003-11-11 18:22 ` viro
2003-11-11 20:15 ` Jonathan Corbet
2003-11-11 18:32 ` Randy.Dunlap
2003-11-11 19:19 ` Anton Blanchard
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=1068580528.26160.12.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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