From: Ingo Molnar <mingo@elte.hu>
To: Jack Steiner <steiner@sgi.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
Mike Travis <travis@sgi.com>
Subject: Re: [PATCH] - Increase MAX_APICS for very large x86_64 configs
Date: Thu, 19 Jun 2008 12:10:30 +0200 [thread overview]
Message-ID: <20080619101030.GF15228@elte.hu> (raw)
In-Reply-To: <20080616170910.GA24930@sgi.com>
* Jack Steiner <steiner@sgi.com> wrote:
> Increase the maximum number of apics when running very large
> configurations. This patch has no affect on most systems.
>
> Signed-off-by: Jack Steiner <steiner@sgi.com>
applied to tip/x86/uv - thanks Jack.
> The patch has no effect on any 32-bit kernel. It adds ~4k to the size
> of 64-bit kernels but only if NR_CPUS > 255.
>
> This is a repost of an earlier patch (4/16) that was implicated in a
> random-qa failure. I have not been able to reproduce the failure using
> the same boot args & config. Best guess is that some other patch
> caused random data corruption & this patch was a victim.
i have just re-tested the previously failing config on tip/master:
http://redhat.com/~mingo/misc/config-Thu_Apr_17_10_17_14_CEST_2008.bad
http://people.redhat.com/mingo/tip.git/README
and the good news is that it does not crash on bootup anymore. Perhaps
one of Mike's fixes/improvements did the trick?
Nevertheless i'll keep an eye on this change and wont propagate it to
linux-next for a few days to make sure it's all robust on a wide range
of x86 testsystems.
Ingo
next prev parent reply other threads:[~2008-06-19 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 17:09 [PATCH] - Increase MAX_APICS for very large x86_64 configs Jack Steiner
2008-06-19 10:10 ` Ingo Molnar [this message]
2008-06-19 10:32 ` Ingo Molnar
2008-06-19 15:02 ` Jack Steiner
2008-06-19 15:17 ` Ingo Molnar
2008-06-19 15:19 ` 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=20080619101030.GF15228@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.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