linux-kernel - Re: [PATCH 1/2] Do not require CONFIG_HIGHMEM64G to set CONFIG

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]

Message-ID: <20080118161719.GA5850@elte.hu>
Date:	Fri, 18 Jan 2008 17:17:19 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mel Gorman <mel@....ul.ie>
Cc:	linux-mm@...ck.org, apw@...dowen.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Do not require CONFIG_HIGHMEM64G to set
	CONFIG_NUMA on x86


* Mel Gorman <mel@....ul.ie> wrote:

> There is nothing inherent in HIGHMEM64G required for CONFIG_NUMA to 
> work. It just limits potential testing coverage so remove the 
> limitation.

thanks Mel, applied. Great change - this will trigger NUMA related build 
(and boot) failures must faster in randconfig testing.

	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/