From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: "Yinghai Lu" <yhlu.kernel@gmail.com>,
"Mike Travis" <travis@sgi.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Dhaval Giani" <dhaval@linux.vnet.ibm.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
"Jack Steiner" <steiner@sgi.com>, "Alan Mayer" <ajm@sgi.com>,
"Cliff Wickman" <cpw@sgi.com>
Subject: Re: kernel BUG at arch/x86/kernel/io_apic_64.c:357!
Date: Wed, 30 Jul 2008 01:00:44 +0100 [thread overview]
Message-ID: <20080730010044.06e7442b@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <m17ib48etp.fsf@frodo.ebiederm.org>
On Tue, 29 Jul 2008 16:12:50 -0700
ebiederm@xmission.com (Eric W. Biederman) wrote:
> "Yinghai Lu" <yhlu.kernel@gmail.com> writes:
>
> >> But this would be a show stopper for SGI being able to ship systems if the
> >> distros do not want to waste this much memory and won't set NR_CPUS=4096.
> >
> > wonder if nr_irqs need to be probed dynamically too.
>
> NR_IRQS simply needs to die.
Agreed - it would also be nice to bite the bullet at the same time and
stop using dev->irq as an integer in an increasingly fake and imaginary
numberspace and instead make it an object with a description and other
properties. That would make "no IRQ" NULL, let us display meaningful IRQ
strings and the like as well as ensuring nobody tries to abuse NR_IRQ and
hardcoded similar knowledge for arrays
Alan
next prev parent reply other threads:[~2008-07-30 0:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:09 Dhaval Giani
2008-07-29 18:35 ` Yinghai Lu
2008-07-29 19:20 ` Yinghai Lu
2008-07-29 20:14 ` Eric W. Biederman
2008-07-29 20:37 ` Yinghai Lu
2008-07-29 22:17 ` Mike Travis
2008-07-29 22:21 ` Yinghai Lu
2008-07-29 23:12 ` Eric W. Biederman
2008-07-30 0:00 ` Alan Cox [this message]
2008-07-30 1:29 ` Eric W. Biederman
2008-07-29 23:12 ` Eric W. Biederman
2008-07-29 23:42 ` Jeremy Fitzhardinge
2008-07-30 0:01 ` Eric W. Biederman
2008-07-30 0:50 ` Jeremy Fitzhardinge
2008-07-30 1:36 ` Eric W. Biederman
2008-08-01 17:48 ` Jeremy Fitzhardinge
2008-07-29 20:21 ` Dhaval Giani
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=20080730010044.06e7442b@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ajm@sgi.com \
--cc=cpw@sgi.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=yhlu.kernel@gmail.com \
/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®