From: Miles Bader <miles.bader@necel.com>
To: linux-kernel@vger.kernel.org
Subject: irq 0?
Date: Mon, 07 Nov 2005 20:54:17 +0900 [thread overview]
Message-ID: <buobr0wbrme.fsf@dhapc248.dev.necel.com> (raw)
I notice that arch/v850/kernel/irq.c has been updated with a
"show_interrupts" function; in this function it contains the following
bit of code:
if (i == 0) {
seq_puts(p, " ");
for (i=0; i < 1 /*smp_num_cpus*/; i++)
seq_printf(p, "CPU%d ", i);
seq_putc(p, '\n');
}
if (i < NR_IRQS) {
... show interrupt i ...
} else if (i == NR_IRQS)
seq_printf(p, "ERR: %10lu\n", irq_err_count);
where "i" is iterated (by procfs) from 0...NR_IRQS.
On the v850, irq 0 is a real interrupt, so this doesn't really work
properly -- it doesn't display an entry for irq 0.
Is it now illegal for irq 0 to be a real interrupt (was it illegal before)?
Or is the procfs code just bogus?
Thanks,
-miles
--
Occam's razor split hairs so well, I bought the whole argument!
next reply other threads:[~2005-11-07 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 11:54 Miles Bader [this message]
2005-11-07 12:25 ` irq 0? Ian Campbell
2005-11-07 12:57 ` Miles Bader
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=buobr0wbrme.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.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