Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/Arc-Compute/Mdev-GPU
A user-configurable utility for GPU vendor drivers enabling the registration of arbitrary mdev types with the VFIO-Mediated Device framework.
https://github.com/Arc-Compute/Mdev-GPU
Last synced: 2 months ago
JSON representation
A user-configurable utility for GPU vendor drivers enabling the registration of arbitrary mdev types with the VFIO-Mediated Device framework.
- Host: GitHub
- URL: https://github.com/Arc-Compute/Mdev-GPU
- Owner: Arc-Compute
- License: gpl-2.0
- Created: 2022-06-23T15:42:32.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2022-08-22T20:50:42.000Z (over 2 years ago)
- Last Synced: 2024-08-02T01:26:36.607Z (6 months ago)
- Language: Haskell
- Homepage: https://docs.linux-gvm.org/
- Size: 47.9 KB
- Stars: 54
- Watchers: 3
- Forks: 2
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- Changelog: ChangeLog.md
- License: LICENSE
Awesome Lists containing this project
README
# Mdev GPU
Mdev-GPU is a user-configurable utility for GPU vendor drivers enabling the registration of arbitrary mdev types with the VFIO-Mediated Device framework.
Mdev-GPU is released under GPLv2 as one component of the [GPU Virtual Machine (GVM) Project](https://gvm-docs.openmdev.io/).
# How do I use Mdev-GPU?
- [Documentation for Mdev-GPU](https://openmdev.io/index.php/Mdev-GPU)
# What does Mdev-GPU do?
GPU virtualization is not widely supported using free(libre) driver programs on commodity GPUs.
Mdev-GPU enables the creation of arbitrary user-configurable Mediated Device types on existing drivers which either don't support [VFIO-Mdev functionality](https://openmdev.io/index.php/Virtual_I/O_Internals#Mdev_Mode) or only support pre-defined Mdev types.
# How does this work?
In order to virtualize the GPU via the VFIO-Mdev API a driver must register devices and mdev callbacks with the Mediated Core.
This may be accomplished via the vendor driver in the case that it supports pre-defined mdev types or via GVM/Mdev-GPU for drivers which do not include support for Mdev functionality and/or do not support arbitrary Mdev types.
A diagram below depicts the components Mdev-GPU interacts with.
For further information see the Virtual I/O Internals article on OpenMdev.io under the section titled [Registering PCIE Device with the Mediated Core](https://openmdev.io/index.php/Virtual_I/O_Internals#Registering_PCIE_Device_with_the_Mediated_Core).
# What programs work with Mdev-GPU?
If you are running a program which interacts with the [VFIO-Mdev API](https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/tree/Documentation/driver-api/vfio-mediated-device.rst) then you can install Mdev-GPU underneath it without modifying your programs or changing your workflow.
Here is a list of some existing programs that can interact with functionality enabled by Mdev-GPU without modification:
- [LibVirt](https://libvirt.org/)
- [LibVF.IO](https://libvf.io/)
- [mdevctl](https://github.com/mdevctl/mdevctl)
# Learn More
- [Documentation from the OpenMdev Foundation](https://openmdev.io)
# Compilation
To compile this program run the following commands:
`curl -sSL https://get.haskellstack.org/ | sh`
`stack install`
The resulting binary file or files (depending on which GVM Project sources are compiled) will be located in ~/.local/bin/
This program can take some time to compile (around 10 minutes depending on your system) so if you would prefer to use a pre-built binary instead they are made available under [Releases](https://github.com/Arc-Compute/Mdev-GPU/releases).