Public bug reported:
SVM is short for shared virtual memory. This task is aiming at enabling
SVM support for assigned devices on KVM. Example: assign a GPU from host
to guest, the application program running in guest could share its
virtual memory address to the assigned device.
Latest update: extend the vIOMMU in QEMU to support SVM feature.
1. Description of the Technology.
SVM is shorted for Shared Virtual Memory, it is a VT-d feature that allows
sharing application virtual address space with the I/O device. The feature
works with the PCI sig Process Address Space ID (PASID). SVM has the following
benefits:
• Programmer gets a consistent view of memory across host application and device
• Efficient access to data, avoiding pining or copying overheads
2. Use cases that is important for this technology (aka, why is this technology
needed).
Intel has multiple IPs that would support SVM, and the usage in guest is also a
demand. e.g. QAT, it is usual to assign a QAT to guest and requires SVM to
benefit from its advantages.
3. General design description (components modified: kvm, qemu-kvm, driver,
libvirt (and other userland libraries))
Modified components would include: qemu-kvm, vfio driver, iommu driver
Target Linux 5.19
** Affects: kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954473
Title:
KVM Shared Virtual Memory (SVM)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1954473/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
