aboutsummaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel
diff options
context:
space:
mode:
authorBjorn Helgaas <bjorn.helgaas@hp.com>2010-10-26 17:41:54 -0400
committerJesse Barnes <jbarnes@virtuousgeek.org>2010-10-26 18:33:45 -0400
commit1af3c2e45e7a641e774bbb84fa428f2f0bf2d9c9 (patch)
tree039efdb6eecc9d28e7bef5486a1b02527838c23d /arch/x86/kernel
parent419afdf53cca794a190014593b4778e2e9d64cf3 (diff)
x86: allocate space within a region top-down
Request that allocate_resource() use available space from high addresses first, rather than the default of using low addresses first. The most common place this makes a difference is when we move or assign new PCI device resources. Low addresses are generally scarce, so it's better to use high addresses when possible. This follows Windows practice for PCI allocation. Reference: https://bugzilla.kernel.org/show_bug.cgi?id=16228#c42 Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'arch/x86/kernel')
-rw-r--r--arch/x86/kernel/setup.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 922b5a1f978b..0fe76df866db 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -788,6 +788,7 @@ void __init setup_arch(char **cmdline_p)
788 788
789 x86_init.oem.arch_setup(); 789 x86_init.oem.arch_setup();
790 790
791 resource_alloc_from_bottom = 0;
791 iomem_resource.end = (1ULL << boot_cpu_data.x86_phys_bits) - 1; 792 iomem_resource.end = (1ULL << boot_cpu_data.x86_phys_bits) - 1;
792 setup_memory_map(); 793 setup_memory_map();
793 parse_setup_data(); 794 parse_setup_data();