VFIO-Mdev_Samples
Kernel-Support
| VFIO-Mdev_Samples | Kernel-Support | |
|---|---|---|
| 1 | 1 | |
| 0 | 0 | |
| - | - | |
| 0.0 | 1.8 | |
| over 1 year ago | over 2 years ago | |
| C | ||
| GNU General Public License v3.0 only | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
VFIO-Mdev_Samples
-
GVM: A GPU Virtual Machine for Iommu-Capable Computers
https://github.com/OpenMdev/VFIO-Mdev_Samples
> I'm not confused either about how GVM/mdev-gpu works or about its relation to libvf.io. It's not hard to read between the missing lines of your project roadmap.
You define types that are presented in mdevctl via a YAML config file the user can write themselves or via a JSON file. So LibVF.IO might as well be entirely ignorant to the fact that GVM is on the system. All it sees are different arbitrary mdev types that the user decides to create. Not sure where you're going with this comment.
>I read this before I ever wrote a reply, which you should have guessed because there was no other way to get any information. None of it tells anyone WHY this should use this instead of the bindings which have 100 developers on them, which have been battle tested for years, and for which the original author of VFIO wrote exhaustive, excellent manuals on the blog I linked earlier 7.5 years ago.
>What advantages does your system offer?
Well for starters I've never argued LibVF.IO is better than libvirt. In-fact when folks bring it up I generally say there's a lot we can learn from libvirt.
Kernel-Support
What are some alternatives?
linux-intel-lts
LibVF.IO - A vendor neutral GPU multiplexing tool driven by VFIO & YAML.
GVM-user - GVM-user.
gvt-linux
Mdev-GPU - A user-configurable utility for GPU vendor drivers enabling the registration of arbitrary mdev types with the VFIO-Mediated Device framework.