3 ms·
Based 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 c
by ArcVRArthur 5y ago
Based 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.