From: "Yinghai Lu" <yinghai@kernel.org>
To: "Ben Hutchings" <bhutchings@solarflare.com>
Cc: "Cyrill Gorcunov" <gorcunov@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Don't allow nr_irqs > NR_IRQS
Date: Tue, 4 Nov 2008 10:56:05 -0800 [thread overview]
Message-ID: <86802c440811041056p631e2dc9i21c4994e3d01cf32@mail.gmail.com> (raw)
In-Reply-To: <1225823807.3074.24.camel@achroite>
On Tue, Nov 4, 2008 at 10:36 AM, Ben Hutchings
<bhutchings@solarflare.com> wrote:
> On Tue, 2008-11-04 at 21:00 +0300, Cyrill Gorcunov wrote:
> [...]
>> | I hit this when running net-next-2.6 (close to 2.6.28-rc3) on a
>> | Supermicro dual Xeon system. NR_IRQS is 224 but probe_nr_irqs() detects
>> | 5 IOAPICs (!) and returns 240. Here are the log messages:
>> |
>
> Well there must have been an earlier change that resulted in detecting 5
> IOAPICs instead of just 1, but that presumably would work as long as the
> irq_desc array was dynamically allocated. This reversion breaks that.
>
> You don't really need to see the config; NR_IRQS is *always* 224 on
> normal x86-32 systems.
>
Yes. it should the same as setting to 64bit. we will cost some extra ram...
We can not make sparseirq/dyn_array to 2.6.28..., maybe 2.6.29 later.
Ingo,
Maybe we can put back dyn_array at first, that will still be 1:1
mapping..., and not waste memory..
YH
next prev parent reply other threads:[~2008-11-04 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 17:18 Ben Hutchings
2008-11-04 18:00 ` Cyrill Gorcunov
2008-11-04 18:36 ` Ben Hutchings
2008-11-04 18:56 ` Yinghai Lu [this message]
2008-11-04 19:01 ` Cyrill Gorcunov
[not found] ` <1225825559.3074.26.camel@achroite>
[not found] ` <20081104194606.GJ21470@localhost>
2008-11-04 21:31 ` Ben Hutchings
2008-11-05 12:04 ` [PATCH v2] " Ben Hutchings
2008-11-05 19:11 ` Cyrill Gorcunov
2008-11-05 19:15 ` Ben Hutchings
2008-11-05 19:26 ` Cyrill Gorcunov
2008-11-06 9:03 ` Ingo Molnar
2008-11-06 6:24 ` Ingo Molnar
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=86802c440811041056p631e2dc9i21c4994e3d01cf32@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=bhutchings@solarflare.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®