CONFIG_NR_CPUS limit for 32-bit
Given that the fixmap area size depends on NR_CPUS and that it can't possibly cover 4096 CPUs (its size would be beyond 200Mb if I put things together correctly, whereas the vmalloc area [of which the fixmap area is a sub-portion] by default is 128MB) I can't see how this new limit ought to even boot on any system.
Therefore I wonder whether the range shouldn't be restricted for X86_32.
Jan