Re: [PATCH v14 04/11] numa: Extend CLI to provide initiator information for numa nodes

[Eric Blake]

On 10/28/19 2:52 AM, Tao Xu wrote:
> In ACPI 6.3 chapter 5.2.27 Heterogeneous Memory Attribute Table (HMAT),
> The initiator represents processor which access to memory. And in 5.2.27.3
> Memory Proximity Domain Attributes Structure, the attached initiator is
> defined as where the memory controller responsible for a memory proximity
> domain. With attached initiator information, the topology of heterogeneous
> memory can be described.
>
> Extend CLI of "-numa node" option to indicate the initiator numa node-id.
> In the linux kernel, the codes in drivers/acpi/hmat/hmat.c parse and report
> the platform's HMAT tables.
>
> Reviewed-by: Igor Mammedov <address@hidden>
> Reviewed-by: Jingqi Liu <address@hidden>
> Suggested-by: Dan Williams <address@hidden>
> Signed-off-by: Tao Xu <address@hidden>
> ---

> +++ b/qapi/machine.json
> @@ -463,6 +463,13 @@
>   # @memdev: memory backend object.  If specified for one node,
>   #          it must be specified for all nodes.
>   #
> +# @initiator: defined in ACPI 6.3 Chapter 5.2.27.3 Table 5-145,
> +#             points to the nodeid which has the memory controller
> +#             responsible for this NUMA node. This field provides
> +#             additional information as to the initiator node that
> +#             is closest (as in directly attached) to this node, and
> +#             therefore has the best performance (since 4.2)
> +#

I'm sad to say, but we've now missed soft freeze for 4.2.  This feels 
like enough of a feature that we'll probably have to defer the series to 
the 5.0 release, which will have ripple effects to your patches.

--
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org