| 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
| ||
|
Message-ID: <84144f020904211125v68b98df4ke1c04bc29df65fda@mail.gmail.com> Date: Tue, 21 Apr 2009 21:25:31 +0300 From: Pekka Enberg <penberg@...helsinki.fi> To: Christoph Lameter <cl@...ux.com> Cc: "Luck, Tony" <tony.luck@...el.com>, Nick Piggin <npiggin@...e.de>, linux-kernel@...r.kernel.org, randy.dunlap_ocs10g@...cle.com, Andrew Morton <akpm@...ux-foundation.org>, Paul Mundt <lethal@...ux-sh.org>, iwamatsu.nobuhiro@...esas.com Subject: Re: linux-next ia64 build problems in slqb On Tue, Apr 21, 2009 at 1:08 AM, Luck, Tony <tony.luck@...el.com> wrote: >> > The ia64 "allnoconfig" build ends up with the (possibly dubious) combination >> > of .config options: >> > >> > CONFIG_SMP=n >> > CONFIG_NUMA=y >> >> Yeah, I don't think the combination makes much sense and x86 doesn't >> allow it. Can we fix that in ia64 Kconfig? That said, this seems to >> come up with every architecture except x86, so if someone is kind >> enough to send me a tested fix for slqb, I'll just go ahead and apply >> it. On Tue, Apr 21, 2009 at 5:35 PM, Christoph Lameter <cl@...ux.com> wrote: > Tony runs tests with this configuration. This is an established > configuration and has been historically supported. Interesting. What exactly is an UP NUMA machine? Anyway, I'm more than happy to apply a tested patch to fix up SLQB. Nick? -- 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/
Powered by blists - more mailing lists