Subject: Re: bin/20316: systat interrupt counters
To: David Laight <firstname.lastname@example.org>
From: Johnny Billquist <email@example.com>
Date: 02/13/2003 01:09:11
On Thu, 13 Feb 2003, David Laight wrote:
> If you include the group names the above looks like:
> Which is completely worse than useless! Which is why I split the
> available space equally between the group and event names.
> However that didn't really work either since you need 5 or 6 chars
> to make sense of some of the names - hence the "don't display <= 3
> chars of group name" test.
Yes, that is about as worthless as using the name field alone on VAX...
> In actual fact the 'pic0 pin %d' strings could probably be changed
> to something more meangful. After all 'pins' 8-15 are actually on
> pic1. Also on a PC some of them are definitely allocated to specific
> hardware. Maybe it is poddibly to work out which driver attached to
> the IRQ?
I'm actually a bit surprised that the PC don't make a better effort. After
all, it should know which device each interrupt goes to at the time the
probing occurs, don't it? It says more intelligent things on the console
during autoconf anyway. Shouldn't that information be stored in the evcnt
structure instead of just saying which pin on the pic it is (which
actually is incorrect, since pins 8-15 is on pic1, and not pic0).
While I don't want to stumble into a religour war, it seems as if
perhaps the i386-port should change here?
Let's get the actual device names in there. It would be much nicer to see
"ex0 intr" instead of "pic0 pin 11". :-)
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: firstname.lastname@example.org || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol