linux-kernel - Re: [PATCH] x86: unify "numa=" command line option handling

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]

Message-Id: <4D2ACE08020000780002B481@vpn.id2.novell.com>
Date:	Mon, 10 Jan 2011 08:14:48 +0000
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	"Ingo Molnar" <mingo@...e.hu>,
	"David Rientjes" <rientjes@...gle.com>
Cc:	"Tejun Heo" <tj@...nel.org>, <tglx@...utronix.de>,
	<linux-kernel@...r.kernel.org>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86: unify "numa=" command line option handling

>>> On 07.01.11 at 20:55, David Rientjes <rientjes@...gle.com> wrote:
> I still don't think it meets the stable kernel rules.  The changelog 
> explicitly states that we do not want to disable ACPI completely, so the 
> only numa= command line option that would possibly be useful on 32-bit is 
> numa=off in this case.  If you're compiling a 32-bit kernel for a machine 
> with SRAT entries that can't be parsed by the kernel, then there's still 
> no explanation as to why CONFIG_NUMA=n won't fix it.

In distro kernels you have no control over the configuration, yet you
may want the kernel to boot on a particular machine.

Jan

--
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/