From: Matthew Wilcox <matthew@wil.cx>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Matthew Wilcox <willy@parisc-linux.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] [2/5] Improve 53c700 /proc/interrupt output
Date: Sat, 19 Mar 2005 16:23:07 +0000 [thread overview]
Message-ID: <20050319162307.GM21986@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1111247587.5525.7.camel@mulgrave>
On Sat, Mar 19, 2005 at 09:53:07AM -0600, James Bottomley wrote:
> On Fri, 2005-03-18 at 20:56 -0700, Matthew Wilcox wrote:
> > Request the IRQ in the name of the chip rather than the bus address.
>
> This I don't really like for two reasons:
>
> 1) I don't know of any other driver that uses the actual chip name in
> the interrupt (most use either the driver name or the module name)
I'm fine with that.
> 2) As someone with a large number of these things in a single box,
> knowing which actual device is going up in /proc/interrupts is valuable
> to me
You can get that information through /sys ...
# for i in /sys/class/scsi_host/*; do echo -n "`basename $i` "; irq=`cat $i/device/../irq`; grep $irq /proc/interrupts; done
host0 67: 11349 CPU zalon
host1 68: 15 CPU zalon
host2 16: 50 GSC-ASIC 53c710
> How about I look at abstracting the name so that the glue driver (in
> your case lasi700) can set the name?
That would work too ...
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-03-19 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 3:56 [PATCH] [2/5] Improve 53c700 /proc/interrupt output Matthew Wilcox
2005-03-19 15:53 ` James Bottomley
2005-03-19 16:23 ` Matthew Wilcox [this message]
2005-03-21 2:56 ` James Bottomley
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=20050319162307.GM21986@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.