4 ms·
vGPU_Unlock's Merged driver is an optional package you can include but if you don't want to use it there's no explicit dependance. We actually enable these feat
by ArcVRArthur 5y ago
vGPU_Unlock's Merged driver is an optional package you can include but if you don't want to use it there's no explicit dependance. We actually enable these features using a vendor neutral API called VFIO-Mdev:
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/tree/Documentation/driver-api/vfio-mediated-device.rst?h=driver-core-next&id=7de3697e9cbd4bd3d62bafa249d57990e1b8f294 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/drive...
Here's a few examples of YAML for use with different GPU vendors:
Intel: https://github.com/Arc-Compute/libvf.io/blob/master/example/intel-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/...
Nvidia: https://github.com/Arc-Compute/libvf.io/blob/master/example/nvidia-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/...
AMD: https://github.com/Arc-Compute/libvf.io/blob/master/example/amd-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/...
The odd one out is AMD that uses a different API due to the fact that the vendor has largely ignored standard open source interfaces in the kernel. We're still supporting that API but unfortunately there are very few AMD cards that work due to the fact that they refuse to release open source code to support their newer cards and they have locked out these features at the firmware level on consumer cards. Fortunately Nvidia and Intel GPUs are very well suited to this functionality and we've got support for most recent consumer cards from both!
- InvaderFizz 5y agoIt would be helpful to note that Intel GVT-g is a dead end with 10th gen Comet Lake being the end of the road[0]. They do not support it with XE and have instead decided to go with SR-IOV. I'm curious to see if this could be used in virtualizing macOS with GVT-g for 3D accelerated guests. I know that this was looked at a few year ago and no one had made it work then. 0: https://github.com/torvalds/linux/blob/2f111a6fd5b5297b4e92f53798ca086f7c7d33a4/drivers/gpu/drm/i915/intel_gvt.c#L44-L60 https://github.com/torvalds/linux/blob/2f111a6fd5b5297b4e92f...
- ArcVRArthur 5y agoBased on my reading of the link you provided I don't believe support for GVT-g has been removed. You can see the GVT-Linux repository is also still receiving commits: https://github.com/intel/gvt-linux https://github.com/intel/gvt-linux
- InvaderFizz 5y agoTo be clear, I never said it was dead, only a dead end. As for GVT-g and Xe, according to a post in this[0] issue by one of the Intel devs, Rocket Lake (Xe) is not getting support and only does GVT-d. Also in the same issue, someone pointed out that Intel themselves have states as much here[1]. I hope I am proven wrong in the end and GVT-g comes to then entire Xe and ARC lineup. Intel's communication on this matter has been...lacking. 0: https://github.com/intel/gvt-linux/issues/190 https://github.com/intel/gvt-linux/issues/190 1: https://www.intel.com/content/www/us/en/support/articles/000058558/graphics.html https://www.intel.com/content/www/us/en/support/articles/000...
- iforgotpassword 5y agoWas on a call with Intel last week and they specifically confirmed there are no plans to bring GVT-g back. :-( Makes sense as in servers you probably want static partitioning anyways, but for desktop it was perfect.
- ArcVRArthur 5y agoIf they switch GVT-g for SR-IOV that shouldn't affect the use of VFIO-Mdev on consumer devices (the primary API we use). https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/tree/Documentation/driver-api/vfio-mediated-device.rst?h=driver-core-next&id=7de3697e9cbd4bd3d62bafa249d57990e1b8f294 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/drive... It may be that they're changing internal APIs used for device mediation which wouldn't surprise me given both AMD and Nvidia use SR-IOV but only Intel uses GVT-g.