x86: don't initialize sibling and core maps during preparation
it is redundant, since it is already done by set_cpu_sibling_map() Signed-off-by: Glauber Costa <gcosta@redhat.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
committed by
Ingo Molnar
parent
50e440aa53
commit
e7f8b14e02
@@ -855,18 +855,6 @@ static void __init smp_boot_cpus(unsigned int max_cpus)
|
|||||||
++kicked;
|
++kicked;
|
||||||
}
|
}
|
||||||
|
|
||||||
/*
|
|
||||||
* construct cpu_sibling_map, so that we can tell sibling CPUs
|
|
||||||
* efficiently.
|
|
||||||
*/
|
|
||||||
for_each_possible_cpu(cpu) {
|
|
||||||
cpus_clear(per_cpu(cpu_sibling_map, cpu));
|
|
||||||
cpus_clear(per_cpu(cpu_core_map, cpu));
|
|
||||||
}
|
|
||||||
|
|
||||||
cpu_set(0, per_cpu(cpu_sibling_map, 0));
|
|
||||||
cpu_set(0, per_cpu(cpu_core_map, 0));
|
|
||||||
|
|
||||||
smpboot_setup_io_apic();
|
smpboot_setup_io_apic();
|
||||||
|
|
||||||
setup_boot_clock();
|
setup_boot_clock();
|
||||||
|
Reference in New Issue
Block a user