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
| ||
|
Date: Fri, 8 Jun 2007 10:07:52 +0200 (MEST) From: Mikael Pettersson <mikpe@...uu.se> To: linux-kernel@...r.kernel.org, wli@...omorphy.com Cc: ak@...e.de, akpm@...ux-foundation.org, lkml@....ca Subject: Re: divorce CONFIG_X86_PAE from CONFIG_HIGHMEM64G On Thu, 7 Jun 2007 19:35:51 -0700, William Lee Irwin III wrote: > @@ -573,12 +574,12 @@ > config VMSPLIT_3G > bool "3G/1G user/kernel split" > config VMSPLIT_3G_OPT > - depends on !HIGHMEM > + depends on !X86_PAE > bool "3G/1G user/kernel split (for full 1G low memory)" > config VMSPLIT_2G > bool "2G/2G user/kernel split" > config VMSPLIT_2G_OPT > - depends on !HIGHMEM > + depends on !X86_PAE > bool "2G/2G user/kernel split (for full 2G low memory)" > config VMSPLIT_1G > bool "1G/3G user/kernel split" Is this really needed? I can see why VMSPLIT_{2,3}G_OPT would depend on !HIGHMEM, but why would they depend on !X86_PAE? - 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