From: Markus Armbruster <armbru@redhat.com>
To: <ankita@nvidia.com>
Cc: <jgg@nvidia.com>, <alex.williamson@redhat.com>,
<clg@redhat.com>, <shannon.zhaosl@gmail.com>,
<peter.maydell@linaro.org>, <ani@anisinha.ca>,
<berrange@redhat.com>, <eduardo@habkost.net>,
<imammedo@redhat.com>, <mst@redhat.com>, <eblake@redhat.com>,
<armbru@redhat.com>, <david@redhat.com>, <gshan@redhat.com>,
<Jonathan.Cameron@huawei.com>, <aniketa@nvidia.com>,
<cjia@nvidia.com>, <kwankhede@nvidia.com>,
<targupta@nvidia.com>, <vsethi@nvidia.com>,
<acurrid@nvidia.com>, <dnigam@nvidia.com>, <udhoke@nvidia.com>,
<qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 1/3] qom: new object to associate device to numa node
Date: Fri, 13 Oct 2023 15:16:52 +0200 [thread overview]
Message-ID: <87sf6efyrf.fsf@pond.sub.org> (raw)
In-Reply-To: <20231007201740.30335-2-ankita@nvidia.com> (ankita@nvidia.com's message of "Sun, 8 Oct 2023 01:47:38 +0530")
<ankita@nvidia.com> writes:
> From: Ankit Agrawal <ankita@nvidia.com>
>
> The CPU cache coherent device memory can be added as NUMA nodes
> distinct from the system memory nodes. These nodes are associated
> with the device and Qemu needs a way to maintain this link.
>
> Introduce a new acpi-generic-initiator object to allow host admin
> provide the device and the corresponding NUMA node. Qemu maintain
> this association and use this object to build the requisite GI
> Affinity Structure.
>
> The admin provides the id of the device and the NUMA node id such
> as in the following example.
> -device vfio-pci-nohotplug,host=<bdf>,bus=pcie.0,addr=04.0,rombar=0,id=dev0 \
> -object acpi-generic-initiator,id=gi0,device=dev0,node=2 \
>
> Signed-off-by: Ankit Agrawal <ankita@nvidia.com>
[...]
> diff --git a/qapi/qom.json b/qapi/qom.json
> index fa3e88c8e6..86c87a161c 100644
> --- a/qapi/qom.json
> +++ b/qapi/qom.json
> @@ -779,6 +779,20 @@
> { 'struct': 'VfioUserServerProperties',
> 'data': { 'socket': 'SocketAddress', 'device': 'str' } }
>
> +##
> +# @AcpiGenericInitiatorProperties:
> +#
> +# Properties for acpi-generic-initiator objects.
> +#
> +# @device: the ID of the device to be associated with the node
> +#
> +# @node: the ID of the numa node
> +#
> +# Since: 8.0
Since 8.2
> +##
> +{ 'struct': 'AcpiGenericInitiatorProperties',
> + 'data': { 'device': 'str', 'node': 'uint32' } }
> +
> ##
> # @RngProperties:
> #
> @@ -947,7 +961,8 @@
> 'tls-creds-x509',
> 'tls-cipher-suites',
> { 'name': 'x-remote-object', 'features': [ 'unstable' ] },
> - { 'name': 'x-vfio-user-server', 'features': [ 'unstable' ] }
> + { 'name': 'x-vfio-user-server', 'features': [ 'unstable' ] },
> + 'acpi-generic-initiator'
Please keep the object types sorted alphabetically.
> ] }
>
> ##
> @@ -1014,7 +1029,8 @@
> 'tls-creds-x509': 'TlsCredsX509Properties',
> 'tls-cipher-suites': 'TlsCredsProperties',
> 'x-remote-object': 'RemoteObjectProperties',
> - 'x-vfio-user-server': 'VfioUserServerProperties'
> + 'x-vfio-user-server': 'VfioUserServerProperties',
> + 'acpi-generic-initiator': 'AcpiGenericInitiatorProperties'
Likewise.
> } }
>
> ##
next prev parent reply other threads:[~2023-10-13 13:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 20:17 [PATCH v2 0/3] acpi: report numa nodes for device memory using GI ankita
2023-10-07 20:17 ` [PATCH v2 1/3] qom: new object to associate device to numa node ankita
2023-10-09 12:26 ` Jonathan Cameron via
2023-10-09 12:26 ` Jonathan Cameron
2023-10-09 12:26 ` Jonathan Cameron via
2023-10-11 17:37 ` Vikram Sethi
2023-10-12 8:59 ` Jonathan Cameron via
2023-10-12 8:59 ` Jonathan Cameron
2023-10-12 8:59 ` Jonathan Cameron via
2023-10-09 21:16 ` Alex Williamson
2023-10-13 13:16 ` Markus Armbruster [this message]
2023-10-17 13:44 ` Ankit Agrawal
2023-10-07 20:17 ` [PATCH v2 2/3] hw/acpi: Implement the SRAT GI affinity structure ankita
2023-10-09 21:16 ` Alex Williamson
2023-10-17 13:51 ` Ankit Agrawal
2023-10-07 20:17 ` [PATCH v2 3/3] qom: Link multiple numa nodes to device using a new object ankita
2023-10-09 12:30 ` Jonathan Cameron via
2023-10-09 12:30 ` Jonathan Cameron
2023-10-09 12:30 ` Jonathan Cameron via
2023-10-09 12:57 ` David Hildenbrand
2023-10-09 21:27 ` Alex Williamson
2023-10-17 14:18 ` Ankit Agrawal
2023-10-09 21:16 ` Alex Williamson
2023-10-17 14:00 ` Ankit Agrawal
2023-10-17 15:21 ` Alex Williamson
2023-10-17 15:28 ` Jason Gunthorpe
2023-10-17 16:54 ` Alex Williamson
2023-10-17 17:24 ` Jason Gunthorpe
2023-10-13 13:17 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf6efyrf.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=acurrid@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=ani@anisinha.ca \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=berrange@redhat.com \
--cc=cjia@nvidia.com \
--cc=clg@redhat.com \
--cc=david@redhat.com \
--cc=dnigam@nvidia.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=gshan@redhat.com \
--cc=imammedo@redhat.com \
--cc=jgg@nvidia.com \
--cc=kwankhede@nvidia.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhaosl@gmail.com \
--cc=targupta@nvidia.com \
--cc=udhoke@nvidia.com \
--cc=vsethi@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.