On Wed, 21 Mar 2018, Peter Zijlstra wrote: > On Wed, Mar 21, 2018 at 01:33:24PM +0800, Dou Liyang wrote: > > How about: > > > > possible_cpus= [s390,x86_64] Set the number of possible CPUs which > > are determined by the ACPI tables MADT or mptables by > > default. possible_cpus=n : n >= 1 enforces the possible > > number to be 'n'. > > While nr_cpus is also be set: nr_cpus=m, choice the > > minimum one for the number of possible CPUs. > > So what is the exact difference between possible_cpus and nr_cpus ? I > konw maxcpus= limits the number of CPUs we bring up, and possible_cpus > limits the possible_map, but I'm not entirely sure what nr_cpus does > here. nr_cpus limits the number of CPUs the kernel will handle. Think of it as a boot time override of NR_CPUs. Way too many commandline switches though. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
