linux-kernel - Re: [PATCH] x86: Make NUMA on 32-bit depend on BROKEN

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] [day] [month] [year] [list]

Date:	Tue, 11 Nov 2008 15:08:58 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Pavel Machek <pavel@...e.cz>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] x86: Make NUMA on 32-bit depend on BROKEN

On Tuesday, 11 of November 2008, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw@...k.pl> wrote:
> 
> > From: Rafael J. Wysocki <rjw@...k.pl>
> > Subject: x86: Make NUMA on 32-bit depend on BROKEN
> > 
> > While investigating the failure of hibernation on 32-bit x86 with 
> > CONFIG_NUMA set, as described in this message 
> > http://marc.info/?l=linux-kernel&m=122634118116226&w=4 I asked some 
> > people for help and I was told that it wasn't really worth the 
> > effort, because CONFIG_NUMA was generally broken on 32-bit x86 
> > systems and it shouldn't be used in such configs.  For this reason, 
> > make CONFIG_NUMA depend on BROKEN instead of EXPERIMENTAL on x86-32.
> 
> Actually, it works just fine on a wide range of 32-bit systems that i 
> have, so NAK.
> 
> Hibernation might not work but that's i believe a NUMA<->HIBERNATION 
> interaction issue, we need to fix that. Regular system bootup and 
> stress-tests work just fine.

OK, so it seems I'll have to find out what exactly happens. :-(

Thanks,
Rafael
--
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/