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

Re: [PATCH] kconfig: adjust NR_CPUS defaults


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: "Orzel, Michal" <michal.orzel@xxxxxxx>
  • Date: Mon, 26 Jan 2026 11:31:56 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=suse.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=9hax5IQVpzAukgGgzVYkk6unbzvHGMAyZVzacTxzeBA=; b=x5/BxbysGJZC4kYbuUxCU1i8HNK3En7UEBu0PGjHq4G9biywKZ+590663P17JWqjyK6S9YC9wxUxg3mwY0P+ya95sJYSNr08CJolQXVWveM30Vs7vQZ99YOgr9BaIUhkpMFdmBEj1k2VYQ4SOPfPdAa7JP26wz5a8fxNgI69Dk7yDLSz4lYmlXQXvxFdWCSwVmmaEz/elDNsswMrKnduUBHTyB8Hta525yCNF6c2I5MWVh122mLn0qWbHnUQWaA+iTGxhJys3X3fgQTVRFBPyzPLFUasswQpENPlkk9z4YJ4ueyZSpiCnzHfIfjE9IOUurN7P0Sfq5oEUEODNsZ0vQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=dOUXqN5Z3OOElaVcMN60Bfnn8JsrgpDXRqYHvYqjsiD084LH0eJmxA8xAsX+cSwkeZ/n1YIxrq3qbF1Rjcprbjuk/OnPJHE4P5oBbeS2d4RW62KqvYx6cDcRnpgm4k9cu54QqJnHXwbA66864fiQCExEcZYJm2y6TAhqUz5mwyzeZ4BuY3Dyaq199bh+5LjUDDZ/7Us9paIzFnB+VLtb7Aw4EpRzIq/8Ts/L9WrEUjpCRLOLGD8sJhO4ILqPjvwT5ReDE1ogMppaGOzhpOuPJ7kwKEBzBlwwAXGhZrecNQwDilUaNRBkFKUQ1CxRN5R4G8NLRX/XqSgv7z+WLIbJBA==
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 26 Jan 2026 10:32:11 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>


On 26/01/2026 11:13, Jan Beulich wrote:
> On 26.01.2026 11:08, Orzel, Michal wrote:
>> On 14/01/2026 12:33, Jan Beulich wrote:
>>> Discussion of a RISC-V change revealed that for PPC and RISC-V we don't
>>> really set any default, but rather rely on internals of kconfig picking
>>> the lowest of the permitted values in such a case. Let's make this
>>> explicit, requiring architectures that mean to permit SMP by default to
>>> explicitly record some sensible value here.
>>>
>>> Leverage the adjustment to the "1" case to simplify all subsequent ones.
>>>
>>> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
>> Reviewed-by: Michal Orzel <michal.orzel@xxxxxxx>
> 
> Thanks.
> 
>> with one question...
>>
>>> ---
>>> For not-yet-SMP-capable ports we might go even further and use
>>>
>>>     range 1 1 if !X86 && (!ARM || MPU)
>>>
>>> at the top. Thoughts? (I've not done this right away as it is liable to
>>> get unwieldy when we have a larger number of SMP-capable ports.)
>>>
>>> --- a/xen/arch/Kconfig
>>> +++ b/xen/arch/Kconfig
>>> @@ -9,11 +9,11 @@ config NR_CPUS
>>>     range 1 1 if ARM && MPU
>> Why not simply && MPU given that MPU is an ARM specific option in our 
>> Kconfig.
> 
> Good question, to be answered by whoever put this here. I guess the 
> anticipation
> may have been that "MPU" might end up meaning something else on another arch, 
> at
> some future point?
Except for this specific case, there is no other use of MPU in non-arch Kconfig
or code, so it's difficult to say. I would be more willing to tie it to Arm, so
that we don't need ARM/CONFIG_ARM before MPU/CONFIG_MPU.

~Michal




 


Rackspace

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