From: ebiederm@xmission.com (Eric W. Biederman)
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "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: Tue, 29 Jul 2008 16:12:50 -0700 [thread overview]
Message-ID: <m17ib48etp.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <86802c440807291521k6e6277b5ta05b180d0d1c963a@mail.gmail.com> (Yinghai Lu's message of "Tue, 29 Jul 2008 15:21:02 -0700")
"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.
Eric
next prev parent reply other threads:[~2008-07-29 23:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:09 kernel BUG at arch/x86/kernel/io_apic_64.c:357! 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 [this message]
2008-07-30 0:00 ` Alan Cox
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=m17ib48etp.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=ajm@sgi.com \
--cc=cpw@sgi.com \
--cc=dhaval@linux.vnet.ibm.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 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.