• Magnus Damm's avatar
    [PATCH] x86_64: Make node boundaries consistent · ffd10a2b
    Magnus Damm authored
    
    
    The current x86_64 NUMA memory code is inconsequent when it comes to node
    memory ranges. The exact behaviour varies depending on which config option
    that is used.
    
    setup_node_bootmem() has start and end as arguments and these are used to
    calculate the size of the node like this: (end - start). This is all fine
    if end is pointing to the first non-available byte. The problem is that the
    current x86_64 code sometimes treats it as the last present byte and sometimes
    as the first non-available byte. The result is that some configurations might
    lose a page at the end of the range.
    
    This patch tries to fix CONFIG_ACPI_NUMA, CONFIG_K8_NUMA and CONFIG_NUMA_EMU
    so they all treat the end variable as the first non-available byte. This is
    the same way as the single node code.
    
    The patch is boot tested on dual x86_64 hardware with the above configurations,
    but maybe the removed code is needed as some workaround?
    Signed-off-by: default avatarMagnus Damm <magnus@valinux.co.jp>
    Signed-off-by: default avatarAndi Kleen <ak@suse.de>
    Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    ffd10a2b