Merged Drivers - Revision history

Arthur at 00:22, 2 March 2023

2023-03-02T00:22:51Z

← Older revision		Revision as of 00:22, 2 March 2023
Line 3:		Line 3:
	In the context of this page the term '''"Merged Driver"''' refers to drivers which ''allow simultaneous acceleration of the host using a device's PF (Physical Function) and acceleration of guests using one or more VFs (Virtual Functions) created using the same device''.		In the context of this page the term '''"Merged Driver"''' refers to drivers which ''allow simultaneous acceleration of the host using a device's PF (Physical Function) and acceleration of guests using one or more VFs (Virtual Functions) created using the same device''.

	Merged functionality is currently supported for drivers which both make use of VFIO-Mdev and SR-IOV functionality depending on the vendor and driver implementation.		Merged functionality is currently supported for drivers which both make use of VFIO-Mdev and SR-IOV functionality depending on the vendor and driver implementation.<blockquote>An absence of critical technical documentation has historically slowed growth and adoption of developer ecosystems for GPU virtualization.

			This [https://creativecommons.org/licenses/by/4.0/ CC-BY-4.0] licensed content can either be used with attribution, or used as inspiration for new documentation, created by GPU vendors for public commercial distribution as developer documentation.

			Where possible, this documentation will clearly label dates and versions of observed-but-not-guaranteed behaviour vs. vendor-documented stable interfaces/behaviour with guarantees of forward or backward compatibility.</blockquote>

	== Intel i915 ==		== Intel i915 ==

Arthur: /* Configuration Parameters */

2022-09-26T14:19:46Z

Configuration Parameters

← Older revision		Revision as of 14:19, 26 September 2022
Line 29:		Line 29:
	# Upon executing [https://openmdev.io/index.php/Virtual_IO_Internals#QEMU_adds_VFIO_device_to_IOMMU_container-group QEMU mdev device initialization] for a second Mdev an IOMMU group binding error occurs in QEMU preventing the device from being brought up.<br />'''''Confirmed affected versions:''' 460.32.01, 460.73.04<br />'''Fixed in:''' 510.xx.xx''		# Upon executing [https://openmdev.io/index.php/Virtual_IO_Internals#QEMU_adds_VFIO_device_to_IOMMU_container-group QEMU mdev device initialization] for a second Mdev an IOMMU group binding error occurs in QEMU preventing the device from being brought up.<br />'''''Confirmed affected versions:''' 460.32.01, 460.73.04<br />'''Fixed in:''' 510.xx.xx''

	=== Configuration ~~Parameters~~ ===		=== Module Configuration ===
	Depending on your use-case the use of some additional parameters when booting the system may be helpful.		Depending on your use-case the use of some additional parameters when booting the system may be helpful.

Arthur: /* Configuration Parameters */

2022-09-26T14:18:45Z

Configuration Parameters

← Older revision		Revision as of 14:18, 26 September 2022
Line 32:		Line 32:
	Depending on your use-case the use of some additional parameters when booting the system may be helpful.		Depending on your use-case the use of some additional parameters when booting the system may be helpful.

	Here is a list of some parameters which may be used when loading the module.		Here is a list of some parameters which may be used when loading the module via GRUB or Systemd-boot.
	{\| class="wikitable"		{\| class="wikitable"
	\|+Module Parameters ~~(GRUB / Systemd-boot)~~		\|+Module Parameters
	!Parameter		!Parameter
	!Description		!Description

Arthur at 14:18, 26 September 2022

2022-09-26T14:18:23Z

← Older revision		Revision as of 14:18, 26 September 2022
Line 28:		Line 28:

	# Upon executing [https://openmdev.io/index.php/Virtual_IO_Internals#QEMU_adds_VFIO_device_to_IOMMU_container-group QEMU mdev device initialization] for a second Mdev an IOMMU group binding error occurs in QEMU preventing the device from being brought up.<br />'''''Confirmed affected versions:''' 460.32.01, 460.73.04<br />'''Fixed in:''' 510.xx.xx''		# Upon executing [https://openmdev.io/index.php/Virtual_IO_Internals#QEMU_adds_VFIO_device_to_IOMMU_container-group QEMU mdev device initialization] for a second Mdev an IOMMU group binding error occurs in QEMU preventing the device from being brought up.<br />'''''Confirmed affected versions:''' 460.32.01, 460.73.04<br />'''Fixed in:''' 510.xx.xx''

			=== Configuration Parameters ===
			Depending on your use-case the use of some additional parameters when booting the system may be helpful.

			Here is a list of some parameters which may be used when loading the module.
			{\| class="wikitable"
			\|+Module Parameters (GRUB / Systemd-boot)
			!Parameter
			!Description
			!Side-Effects
			\|-
			\|cudahost=1
			\|Allows use of CUDA on the host system.
			\|Windows guests may fail.
			\|-
			\|nvidia.vgpukvm=0
			\|Disables GPU virtualization on the host.
			\|
			\|}

	== AMDGPU ==		== AMDGPU ==

Arthur at 15:53, 26 July 2022

2022-07-26T15:53:58Z

← Older revision		Revision as of 15:53, 26 July 2022
Line 1:		Line 1:
	The following page will provide specifications and details on the current state of host DRM + VFIO-Mdev drivers in support of various vendors.		The following page will provide specifications and details on the current state of host DRM + VFIO-Mdev drivers in support of various vendors.

	In the context of this page the term '''"Merged Driver"''' refers to drivers which ''allow simultaneous acceleration of the host using a device's PF (~~physical function~~) and acceleration of guests using one or more VFs (Virtual Functions) created using the same device''.		In the context of this page the term '''"Merged Driver"''' refers to drivers which ''allow simultaneous acceleration of the host using a device's PF (Physical Function) and acceleration of guests using one or more VFs (Virtual Functions) created using the same device''.

	Merged functionality is currently supported for drivers which both make use of VFIO-Mdev and SR-IOV functionality depending on the vendor and driver implementation.		Merged functionality is currently supported for drivers which both make use of VFIO-Mdev and SR-IOV functionality depending on the vendor and driver implementation.

Arthur at 14:21, 25 July 2022

2022-07-25T14:21:04Z

← Older revision		Revision as of 14:21, 25 July 2022
Line 1:		Line 1:
	The following page will provide specifications and details on the current state of host DRM + VFIO-Mdev drivers in support of various vendors.		The following page will provide specifications and details on the current state of host DRM + VFIO-Mdev drivers in support of various vendors.

	In the context of this page the term "~~merged driver~~" refers to drivers which ~~allows~~ simultaneous acceleration of the host using a device's PF (physical function) and acceleration of guests using one or more VFs (Virtual Functions) ~~creating~~ using the same device.		In the context of this page the term '''"Merged Driver"''' refers to drivers which ''allow simultaneous acceleration of the host using a device's PF (physical function) and acceleration of guests using one or more VFs (Virtual Functions) created using the same device''.

	Merged functionality is currently supported for drivers which both make use of VFIO-Mdev and SR-IOV functionality depending on the vendor and driver implementation.		Merged functionality is currently supported for drivers which both make use of VFIO-Mdev and SR-IOV functionality depending on the vendor and driver implementation.

Arthur at 14:19, 25 July 2022

2022-07-25T14:19:54Z

← Older revision		Revision as of 14:19, 25 July 2022
Line 1:		Line 1:
	The following page will provide specifications and details on the current state of host DRM + VFIO-Mdev drivers in support of various vendors.		The following page will provide specifications and details on the current state of host DRM + VFIO-Mdev drivers in support of various vendors.

			In the context of this page the term "merged driver" refers to drivers which allows simultaneous acceleration of the host using a device's PF (physical function) and acceleration of guests using one or more VFs (Virtual Functions) creating using the same device.

			Merged functionality is currently supported for drivers which both make use of VFIO-Mdev and SR-IOV functionality depending on the vendor and driver implementation.

	== Intel i915 ==		== Intel i915 ==

Arthur at 14:15, 18 July 2022

2022-07-18T14:15:26Z

← Older revision		Revision as of 14:15, 18 July 2022
Line 23:		Line 23:
	=== Resolved Issues ===		=== Resolved Issues ===

	# Upon executing [https://openmdev.io/index.php/~~Mediated_Device_Internals~~#QEMU_adds_VFIO_device_to_IOMMU_container-group QEMU mdev device initialization] for a second Mdev an IOMMU group binding error occurs in QEMU preventing the device from being brought up.<br />'''''Confirmed affected versions:''' 460.32.01, 460.73.04<br />'''Fixed in:''' 510.xx.xx''		# Upon executing [https://openmdev.io/index.php/Virtual_IO_Internals#QEMU_adds_VFIO_device_to_IOMMU_container-group QEMU mdev device initialization] for a second Mdev an IOMMU group binding error occurs in QEMU preventing the device from being brought up.<br />'''''Confirmed affected versions:''' 460.32.01, 460.73.04<br />'''Fixed in:''' 510.xx.xx''

	== AMDGPU ==		== AMDGPU ==

Arthur: /* Intel i915 */

2022-06-23T17:18:41Z

Intel i915

← Older revision		Revision as of 17:18, 23 June 2022
Line 3:		Line 3:
	== Intel i915 ==		== Intel i915 ==
	[[File:Intel GVT-g Capabilities.png\|thumb\|Intel's slides mention the ability to accelerate up to '8 VMs plus DOM0'. Source: https://01.org/sites/default/files/documentation/an_introduction_to_intel_gvt-g_for_external.pdf]]		[[File:Intel GVT-g Capabilities.png\|thumb\|Intel's slides mention the ability to accelerate up to '8 VMs plus DOM0'. Source: https://01.org/sites/default/files/documentation/an_introduction_to_intel_gvt-g_for_external.pdf]]
	Intel currently supports host DRM and VFIO-Mdev/SR-IOV functionality in it's [https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/i915 current i915 driver sources (GVT-g)] and [https://github.com/intel/linux-intel-lts/commit/41ef979f0894326c202473807a56b599a2f3d04e upstreaming i915 driver sources (SR-IOV)].		Intel currently supports host DRM and VFIO-Mdev/SR-IOV functionality in it's [https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/i915 current i915 driver sources (VFIO-Mdev/GVT-g)] and [https://github.com/intel/linux-intel-lts/commit/41ef979f0894326c202473807a56b599a2f3d04e upstreaming i915 driver sources (VFIO-Mdev/SR-IOV)].

	=== Known Issues ===		=== Known Issues ===

Arthur: /* Intel i915 */

2022-06-23T17:16:31Z

Intel i915

← Older revision		Revision as of 17:16, 23 June 2022
Line 11:		Line 11:
	=== Resolved Issues ===		=== Resolved Issues ===

	# Multiplexing functionality requires use modified KVM and Xen hypervisors ([https://01.org/sites/default/files/documentation/01x08b-kvmgt-a.pdf KVMGT]/[https://wiki.xenproject.org/wiki/XenGT XenGT]). '''''<br />Confirmed affected versions: [https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/i915 current i915 driver sources (GVT-g)]<br />Fixed in: [https://github.com/intel/linux-intel-lts/commit/41ef979f0894326c202473807a56b599a2f3d04e upstreaming i915 driver sources (SR-IOV)]~~'''~~''		# Multiplexing functionality requires use modified KVM and Xen hypervisors ([https://01.org/sites/default/files/documentation/01x08b-kvmgt-a.pdf KVMGT]/[https://wiki.xenproject.org/wiki/XenGT XenGT]). '''''<br />Confirmed affected versions:''' [https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/i915 current i915 driver sources (GVT-g)]'''<br />Fixed in:''' [https://github.com/intel/linux-intel-lts/commit/41ef979f0894326c202473807a56b599a2f3d04e upstreaming i915 driver sources (SR-IOV)]''

	== Nvidia ==		== Nvidia ==