From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: ankita@nvidia.com, jgg@nvidia.com, alex.williamson@redhat.com
Cc: qemu-devel@nongnu.org, qemu-arm <qemu-arm@nongnu.org>
Subject: Re: [RFC v1 2/4] qemu: patch guest SRAT for GPU memory
Date: Tue, 6 Jun 2023 06:58:12 +0200 [thread overview]
Message-ID: <2022d199-3de9-fd34-11ef-bfb11a62a7e1@linaro.org> (raw)
In-Reply-To: <20230605235005.20649-3-ankita@nvidia.com>
On 6/6/23 01:50, ankita@nvidia.com wrote:
> From: Ankit Agrawal <ankita@nvidia.com>
>
> The guest VM adds the GPU memory as (upto 8) separate memory-less NUMA
> nodes. ACPI SRAT need to thus insert proximity domains and tag them as
> MEM_AFFINITY_HOTPLUGGABLE. The VM kernel can then parse the SRAT and
> create NUMA nodes.
>
> Signed-off-by: Ankit Agrawal <ankita@nvidia.com>
> ---
> hw/arm/virt-acpi-build.c | 54 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 54 insertions(+)
>
> diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
> /*
> * ACPI spec, Revision 5.1
> * 5.2.16 System Resource Affinity Table (SRAT)
> @@ -568,6 +620,8 @@ build_srat(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
There is a x86 build_srat() equivalent.
So some abstraction in hw/acpi/srat.c is possible.
> }
>
> + build_srat_devmem(table_data);
> +
> acpi_table_end(linker, &table);
> }
>
next prev parent reply other threads:[~2023-06-06 4:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 23:50 [RFC v1 0/4] Expose GPU memory as coherently CPU accessible ankita
2023-06-05 23:50 ` [RFC v1 1/4] qemu: add GPU memory information as object ankita
2023-06-06 15:19 ` Alex Williamson
2023-06-05 23:50 ` [RFC v1 2/4] qemu: patch guest SRAT for GPU memory ankita
2023-06-06 4:58 ` Philippe Mathieu-Daudé [this message]
2023-06-05 23:50 ` [RFC v1 3/4] qemu: patch guest DSDT " ankita
2023-06-05 23:50 ` [RFC v1 4/4] qemu: adjust queried bar size to power-of-2 ankita
2023-06-06 5:03 ` Philippe Mathieu-Daudé
2023-06-06 12:54 ` Alex Williamson
2023-06-06 14:19 ` Philippe Mathieu-Daudé
2023-06-06 14:54 ` [RFC v1 0/4] Expose GPU memory as coherently CPU accessible Cédric Le Goater
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=2022d199-3de9-fd34-11ef-bfb11a62a7e1@linaro.org \
--to=philmd@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=ankita@nvidia.com \
--cc=jgg@nvidia.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).