From: "Cédric Le Goater" <clegoate@redhat.com>
To: ankita@nvidia.com, jgg@nvidia.com, alex.williamson@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [RFC v1 0/4] Expose GPU memory as coherently CPU accessible
Date: Tue, 6 Jun 2023 16:54:15 +0200 [thread overview]
Message-ID: <877c8a79-6834-3d8a-a8f1-0c115b850821@redhat.com> (raw)
In-Reply-To: <20230605235005.20649-1-ankita@nvidia.com>
Hello Ankit,
On 6/6/23 01:50, ankita@nvidia.com wrote:
> From: Ankit Agrawal <ankita@nvidia.com>
>
> NVIDIA is building systems which allows the CPU to coherently access
> GPU memory. This GPU device memory can be added and managed by the
> kernel memory manager. The patch holds the required changes in QEMU
> to expose this memory to the device assigned VMs.
>
> The GPU device memory region is exposed as device BAR1 and QEMU mmaps to
> it. It then adds new proximity domains to represent the memory in the
> VM ACPI SRAT. This allows the device memory to be added as separate NUMA
> nodes inside the VM. The proximity domains (PXM) are passed to the VM
> using ACPI DSD properties to help VM kernel modules add the memory.
>
> Current Linux cannot create NUMA nodes on the fly, hence creating enough
> NUMA nodes in ACPI is needed so that they are available at the VM bootup
> time. The physical platform firwmare provides 8 NUMA nodes, which QEMU
> is emulating here.
>
> A new vfio-pci variant driver is added to manage the device memory and
> report as a BAR. Ongoing review of the corresponding kernel side changes
> along with the new vfio-pci variant driver.
> Ref: https://lore.kernel.org/lkml/20230405180134.16932-1-ankita@nvidia.com/
>
> Applied over v8.0.2.
>
> Ankit Agrawal (4):
> qemu: add GPU memory information as object
> qemu: patch guest SRAT for GPU memory
> qemu: patch guest DSDT for GPU memory
> qemu: adjust queried bar size to power-of-2
Please use "vfio:" subject prefix when modifying the hw/vfio files.
If you are not sure and want to know what is the current practice,
simply run :
git log --pretty=oneline <files>
Also, to know who to send the series, please use :
./scripts/get_maintainer.pl <patches>
Thanks,
C.
>
> hw/arm/virt-acpi-build.c | 54 ++++++++++++++++++++++++++++
> hw/pci-host/gpex-acpi.c | 71 ++++++++++++++++++++++++++++++++++++
> hw/vfio/common.c | 2 +-
> hw/vfio/pci-quirks.c | 13 +++++++
> hw/vfio/pci.c | 72 +++++++++++++++++++++++++++++++++++++
> hw/vfio/pci.h | 1 +
> include/hw/pci/pci_device.h | 3 ++
> 7 files changed, 215 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2023-06-06 14:55 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é
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 ` Cédric Le Goater [this message]
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=877c8a79-6834-3d8a-a8f1-0c115b850821@redhat.com \
--to=clegoate@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=ankita@nvidia.com \
--cc=jgg@nvidia.com \
--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).