[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1/2] build: introduce CONFIG_NR_CPUS in Kconfig



>>> On 09.01.16 at 14:43, <andrew.cooper3@xxxxxxxxxx> wrote:
> On 08/01/2016 23:17, Doug Goldstein wrote:
>> Introduce an option where the user can modifiy the maximum number of
>> supported physical CPUs.
>>
>> CC: Ian Campbell <ian.campbell@xxxxxxxxxx>
>> CC: Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>
>> CC: Keir Fraser <keir@xxxxxxx>
>> CC: Jan Beulich <jbeulich@xxxxxxxx>
>> CC: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
>> Signed-off-by: Doug Goldstein <cardoe@xxxxxxxxxx>
>> ---
>> This patch can probably be squashed together with the next one but I
>> broke it out with the hope that someone can check the wording on the
>> option and also double check the range.
>> ---
>>  xen/arch/Kconfig     | 8 ++++++++
>>  xen/arch/arm/Kconfig | 2 ++
>>  xen/arch/x86/Kconfig | 2 ++
>>  3 files changed, 12 insertions(+)
>>  create mode 100644 xen/arch/Kconfig
>>
>> diff --git a/xen/arch/Kconfig b/xen/arch/Kconfig
>> new file mode 100644
>> index 0000000..791d577
>> --- /dev/null
>> +++ b/xen/arch/Kconfig
>> @@ -0,0 +1,8 @@
>> +
>> +config NR_CPUS
>> +    int "Maximum number of CPUs"
>> +    range 1 4095
> 
> 4094
> 
> Recursive spinlocks have 12 bit bitfield for cpu, using -1 as a sentinel.

range 1 4095 means CPUs 0...4094, i.e. afaict the range above is
correct.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.