From: Yunsheng Lin
Date: Mon, 2 Sep 2019 14:08:31 +0800
> The NUMA node id in sparc64 system is defined by DT semantics?
Sometimes, and in other cases other methods are used to determine
the NUMA node id.
On 2019/9/1 4:02, David Miller wrote:
> From: Yunsheng Lin
> Date: Sat, 31 Aug 2019 16:57:04 +0800
>
>> Did you mean sparc64 system does not has ACPI, the device's node id will
>> not specified by ACPI, so the ACPI is unrelated here?
>
> Yes, sparc64 never has and never will have ACPI.
>
>
From: Yunsheng Lin
Date: Sat, 31 Aug 2019 16:57:04 +0800
> Did you mean sparc64 system does not has ACPI, the device's node id will
> not specified by ACPI, so the ACPI is unrelated here?
Yes, sparc64 never has and never will have ACPI.
This is also true for several other platforms where you
On 2019/8/31 14:53, David Miller wrote:
> From: Yunsheng Lin
> Date: Sat, 31 Aug 2019 13:58:21 +0800
>
>> According to Section 6.2.14 from ACPI spec 6.3 [1], the setting
>> of proximity domain is optional, as below:
>
> What in the world does the ACPI spec have to do with sparc64 NUMA
> node ID
According to Section 6.2.14 from ACPI spec 6.3 [1], the setting
of proximity domain is optional, as below:
This optional object is used to describe proximity domain
associations within a machine. _PXM evaluates to an integer
that identifies a device as belonging to a Proximity Domain
defined in
From: Yunsheng Lin
Date: Sat, 31 Aug 2019 13:58:21 +0800
> According to Section 6.2.14 from ACPI spec 6.3 [1], the setting
> of proximity domain is optional, as below:
What in the world does the ACPI spec have to do with sparc64 NUMA
node ID checking?
