x86: prepare for cpumask iterators to only go to nr_cpu_ids

Browse source

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>

...

This commit is contained in:

Mike Travis 2008-12-16 17:34:01 -08:00

parent 78637a97b7

commit 168ef543a4

4 changed files with 5 additions and 5 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

arch/x86/kernel/apic.c

View file

2

arch/x86/mach-voyager/voyager_smp.c

View file

4

arch/x86/mm/numa_64.c

View file

2

arch/x86/mm/srat_64.c

View file