Re: [stable] 2.6.23 boot failures on x86-64.

On Mon, 29 Oct 2007, Linus Torvalds wrote:

> We've had some changes since 2.6.23, and afaik, the 
> "alloc_bootmem_high_node()" code is alreadt effectively dead there. It's 
> only called if CONFIG_SPARSEMEM_VMEMMAP is *not* enabled, and I *think* we 
> enable it by force on x86-64 these days.

CONFIG_SPARSEMEM_VMEMMAP was introduced in 2.6.24-rc1.

If I read this Kconfig.x86_64 correctly then it seems that DISCONTIG is 
still the default. Andy?

config ARCH_DISCONTIGMEM_ENABLE
       bool
       depends on NUMA
       default y

config ARCH_DISCONTIGMEM_DEFAULT
        def_bool y
        depends on NUMA

config ARCH_SPARSEMEM_ENABLE
        def_bool y
        depends on (NUMA || EXPERIMENTAL)
        select SPARSEMEM_VMEMMAP_ENABLE

config ARCH_MEMORY_PROBE
        def_bool y
        depends on MEMORY_HOTPLUG

config ARCH_FLATMEM_ENABLE
        def_bool y
        depends on !NUMA
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • 2.6.23 boot failures on x86-64.
    • From: Dave Jones <[email protected]>
  • Re: [stable] 2.6.23 boot failures on x86-64.
    • From: Greg KH <[email protected]>
  • Re: [stable] 2.6.23 boot failures on x86-64.
    • From: Linus Torvalds <[email protected]>

• Prev by Date: Re: [RFC] AGP initial support for chipset flushing..
• Next by Date: Re: [RFC] AGP initial support for chipset flushing..
• Previous by thread: Re: [stable] 2.6.23 boot failures on x86-64.
• Next by thread: Re: [stable] 2.6.23 boot failures on x86-64.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]