Re: Weirdness in __alloc_bootmem_node_high

From: Yinghai Lu
Date: Fri Apr 20 2012 - 15:33:56 EST

On Fri, Apr 20, 2012 at 12:29 PM, Michal Hocko <mhocko@xxxxxxx> 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at