On 11/27/2025 1:05 AM, Peter Krempa wrote:
On Tue, Nov 25, 2025 at 11:17:00 -0800, Nathan Chen via Devel wrote:
[...]
The corresponding qemu command line will include the following arguments:
-object
'{"qom-type":"memory-backend-file","id":"memegm0","mem-path":"/dev/egm4","share":true,"prealloc":true,"size":17179869184}'
\
-object acpi-egm-memory,id=egm0,pci-dev=ua-hostdev0,node=0 \
-object acpi-egm-memory,id=egm1,pci-dev=ua-hostdev1,node=0 \
-numa node,nodeid=0,cpus=0-4,memdev=memegm0 \
Changes from RFCv2:
- Decouple host EGM chardev name from guest EGM ID
- Consolidate all acpi-egm-memory objects' memory into a single
memory-backend-file per EGM chardev specified.
Changes from RFCv1:
- Use existing memory device infrastructure to represent EGM configuration
- Added support for multiple EGM devices
This series is on Github:
https://github.com/NathanChenNVIDIA/libvirt/tree/egm-11-24-25
Thanks,
Nathan
[0]https://lists.libvirt.org/archives/list/[email protected]/
thread/6RU7R2NQEDEUU7JFPM6DTXJBWUDXTYWE/
[1]https://github.com/ianm-nv/qemu/tree/6.8_ghvirt_egm_may2025
[2]https://github.com/NVIDIA/QEMU/
commit/32db1b74fb99c0571724c7e69485e89098c14874
What is the state of this qemu series? I was looking at the aarch64
capability update and didn't see any of the 'acpi-egm-memory' so I went
looking at the qemu mailing list and didn't find any submission adding
the aforementioned object type.
The associated qemu series has not been submitted for upstream feedback
yet, and the underlying kernel series had its first RFC [0] submitted
for upstream review in September of this year.
[0] https://lore.kernel.org/all/[email protected]/
Note that unless the qemu functionallity is commited to the upstream
repository we will not be taking any patches using it.
Understood, we are submitting patches earlier to identify potential
issues with our Libvirt implementation while the qemu portion is being
developed.
