linux-kernel - Re: [PATCH] - Increase MAX_APICS for very large x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Jun 2008 12:10:30 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jack Steiner <steiner@....com>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	Mike Travis <travis@....com>
Subject: Re: [PATCH] - Increase MAX_APICS for very large x86_64 configs


* Jack Steiner <steiner@....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@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/