x86: prepare for cpumask iterators to only go to nr_cpu_ids
authorMike Travis <travis@sgi.com>
Wed, 17 Dec 2008 01:34:01 +0000 (17:34 -0800)
committerMike Travis <travis@sgi.com>
Wed, 17 Dec 2008 01:40:58 +0000 (17:40 -0800)
commit168ef543a43678146e06b3911e987ac021d575b8
tree8539348b5144da9cace8bd7d56bf65d0a1f20554
parent78637a97b7fe1df51f40a460448df0b93d511176
x86: prepare for cpumask iterators to only go to nr_cpu_ids

Impact: cleanup, futureproof

In fact, all cpumask ops will only be valid (in general) for bit
numbers < nr_cpu_ids.  So use that instead of NR_CPUS in various
places.

This is always safe: no cpu number can be >= nr_cpu_ids, and
nr_cpu_ids is initialized to NR_CPUS at boot.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Mike Travis <travis@sgi.com>
Acked-by: Ingo Molnar <mingo@elte.hu>
arch/x86/kernel/apic.c
arch/x86/mach-voyager/voyager_smp.c
arch/x86/mm/numa_64.c
arch/x86/mm/srat_64.c