| 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, 20 Apr 2012 12:32:38 -0700 From: Yinghai Lu <yinghai@...nel.org> To: Michal Hocko <mhocko@...e.cz> Cc: Sam Ravnborg <sam@...nborg.org>, Tejun Heo <tj@...nel.org>, linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: Weirdness in __alloc_bootmem_node_high On Fri, Apr 20, 2012 at 12:29 PM, Michal Hocko <mhocko@...e.cz> wrote: > This is what I can see in the current (Linus) git: > ./arch/sparc/Kconfig: select SPARSEMEM_VMEMMAP_ENABLE > ./arch/powerpc/Kconfig: select SPARSEMEM_VMEMMAP_ENABLE > ./arch/ia64/Kconfig: select SPARSEMEM_VMEMMAP_ENABLE > ./arch/s390/Kconfig: select SPARSEMEM_VMEMMAP_ENABLE > ./arch/s390/Kconfig: select SPARSEMEM_VMEMMAP > ./arch/x86/Kconfig: select SPARSEMEM_VMEMMAP_ENABLE if X86_64 > > So there are more arches which enable SPARSEMEM_VMEMMAP so the function > is used. Or am I missing something? MAX_DMA32_PFN is not defined for them. I was think only x86 have that define. Actually mips have that defined too. Yinghai -- 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