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

Re: [PATCH v2 03/17] xen/arm: implement node distance helpers for Arm


  • To: Wei Chen <Wei.Chen@xxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Thu, 12 Jan 2023 09:11:19 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; 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=TDymfTCZTo/ms0/4p7VbEMIg1/AAMShmhSBVQAO3fpc=; b=aUrJGbSl3TCgLnPkiCTNXpUGsKSQGTqCrp+4sW3/ZWd1MDSKj+Ij+IHf1CqJ3qnh1ow6p0plLXwQCGdRVbqCyKdZsLaIB7BfQSGfysoSCh8bQdWmS0WHGDxiFnLweBIqdFfglC9/I/ih3ULLP+LdRDfpbUQ02Nx6WHnO3Tm2C21XDkbNGEYoOlBQYSiJwUZbuXpAHCMuXiVLA4FpLuKVPxawhjwjKv/+Pjl3AH1hBmRg2q4UuX6VkDqoF88Vfr8x2h+U8sq6pfo2fh5BOidBdDDBWuPGPqF7dKHt/0m0ViLuO0317YInELpwftsEEDohR8/+4wMwXD0MvE5c3shKNQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=O8H+cCLnYeUtZ4rJi+HCktWJdNFdupoL2hPpY4d07Xa4y+CEZVplfe4+vu8guJe6T0nhI6OfBoHfVQ0E89SXZe1EZk/2ROqi4euoCoFWI2J1PoAiPOnFwlvnHFNRSaXC5+1wpkDMvJKNyzIw06Od0MxiGcLUZR8ZOdL8NxL4N+DS60tCBimPUenl5+aNeh/o36RBq/pXgl6l5ylJK3EmqR+YMkQ1bAPIqfmXQ7tTZ9U5pfL/5GQBzV3wWlZhSlFinbWiJSCto/p24/cM6RXWl4mWKQD+5DCQwFeii8PH4eG+YdrBy0x/iD8ytHQYelNJWUMKJxL2GrUNialZMRJfcA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: nd <nd@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 12 Jan 2023 08:11:27 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 12.01.2023 07:31, Wei Chen wrote:
>> -----Original Message-----
>> From: Jan Beulich <jbeulich@xxxxxxxx>
>> Sent: 2023年1月11日 0:47
>>
>> On 10.01.2023 09:49, Wei Chen wrote:
>>> --- a/xen/arch/arm/include/asm/numa.h
>>> +++ b/xen/arch/arm/include/asm/numa.h
>>> @@ -28,6 +28,20 @@ enum dt_numa_status {
>>>      DT_NUMA_OFF,
>>>  };
>>>
>>> +/*
>>> + * In ACPI spec, 0-9 are the reserved values for node distance,
>>> + * 10 indicates local node distance, 20 indicates remote node
>>> + * distance. Set node distance map in device tree will follow
>>> + * the ACPI's definition.
>>> + */
>>> +#define NUMA_DISTANCE_UDF_MIN   0
>>> +#define NUMA_DISTANCE_UDF_MAX   9
>>> +#define NUMA_LOCAL_DISTANCE     10
>>> +#define NUMA_REMOTE_DISTANCE    20
>>
>> In the absence of a caller of numa_set_distance() it is entirely unclear
>> whether this tying to ACPI used values is actually appropriate.
>>
> 
> From Kernel's NUMA device tree binding, it seems DT NUMA are reusing
> ACPI used values for distances [1].

I can't find any mention of ACPI in that doc, so the example values used
there matching ACPI's may also be coincidental. In no event can a Linux
kernel doc serve as DT specification. If values are to match ACPI's, I
expect a DT spec to actually say so.

Jan



 


Rackspace

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