You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| gpu.intel.com/xe_monitoring | Monitoring resource for the `xe` KMD provided devices |
49
49
50
50
For workloads on different KMDs, see [KMD and UMD](#kmd-and-umd).
51
51
@@ -229,28 +229,26 @@ Kubernetes CDI support is included since 1.28 release. In 1.28 it needs to be en
229
229
230
230
### KMD and UMD
231
231
232
-
There are 3 different Kernel Mode Drivers (KMD) available: `i915 upstream`, `i915 backport` and `xe`:
233
-
*`i915 upstream` is a vanilla driver that comes from the upstream kernel and is included in the common Linux distributions, like Ubuntu.
234
-
*`i915 backport` is an [out-of-tree driver](https://github.com/intel-gpu/intel-gpu-i915-backports/) for older enterprise / LTS kernel versions, having better support fornew HW before upstream kernel does. API it provides to user-space can differ from the eventual upstream version.
235
-
*`xe` is a new KMD that is intended to support future GPUs. While it has [experimental support for latest current GPUs](https://docs.kernel.org/gpu/rfc/xe.html) (starting from Tigerlake), it will not support them officially.
232
+
There are 3 different Kernel Mode Drivers (KMDs) available:
233
+
*`i915` ([out-of-tree](https://github.com/intel-gpu/intel-gpu-i915-backports/)): official driver for Data Center GPUs, supporting only limited set of enterprise / LTS kernel versions.
234
+
*`i915` (upstream): official upstream kernel driver forolder Intel client GPUs. Includedin the common Linux distributions like Ubuntu.
235
+
*`xe`: official upstream kernel driver forthe latest (Xe2 or newer architecture) Intel GPUs.
236
236
237
-
For optimal performance, the KMD should be paired with the same UMD variant. When creating a workload container, depending on the target hardware, the UMD packages should be selected approriately.
237
+
Although given KMD may seem to work fine also on other hardware (HW), it's validated only for [hardware it officially supports](https://dgpu-docs.intel.com/devices/hardware-table.html), and can have problems on others. User-space APIs also differ between these KMDs, so care should be taken to ensure that User Space Drivers (UMDs) within containers match KMDs used on the nodes they run, e.g. by them being installed from the same repository.
238
238
239
-
| KMD | UMD packages | Support notes |
239
+
| KMD | KMD / UMD packages | Support notes |
240
240
|:---- |:-------- |:------- |
241
-
|`i915 upstream`| Distro Repository | For Integrated GPUs. Newer Linux kernels will introduce support for Arc, Flex or Max series. |
242
-
|`i915 backport`| [Intel Repository](https://dgpu-docs.intel.com/driver/installation.html#install-steps) | Best for Arc, Flex and Max series. Untested for Integrated GPUs. |
243
-
|`xe`| Source code only | Experimental support for Arc, Flex and Max series. |
244
-
245
-
>*NOTE*: Xe UMD is in active development and should be considered as experimental.
241
+
| `i915` (out-of-tree) | [Intel Repository](https://dgpu-docs.intel.com/driver/installation.html) | For Flex and Max series Data Center GPUs. |
| `xe` | Distro or [Intel Repository](https://dgpu-docs.intel.com/driver/client/overview.html) | For discrete Battlemage, integrated LunarLake, and newer GPUs. |
246
244
247
245
Creating a workload that would support all the different KMDs is not currently possible. Below is a table that clarifies how each domain supports different KMDs.
| Compute | Default |[NEO_ENABLE_i915_PRELIM_DETECTION](https://github.com/intel/compute-runtime/blob/3341de7a0d5fddd2ea5f505b5d2ef5c13faa0681/CMakeLists.txt#L496-L502)|[NEO_ENABLE_XE_DRM_DETECTION](https://github.com/intel/compute-runtime/blob/3341de7a0d5fddd2ea5f505b5d2ef5c13faa0681/CMakeLists.txt#L504-L510)|All three KMDs can be supported at the same time. |
252
-
| Media | Default |[ENABLE_PRODUCTION_KMD](https://github.com/intel/media-driver/blob/a66b076e83876fbfa9c9ab633ad9c5517f8d74fd/CMakeLists.txt#L58)|[ENABLE_XE_KMD](https://github.com/intel/media-driver/blob/a66b076e83876fbfa9c9ab633ad9c5517f8d74fd/media_driver/cmake/linux/media_feature_flags_linux.cmake#L187-L190)|Xe with upstream or backport i915, not all three. |
253
-
| Graphics | Default |Unknown|[intel-xe-kmd](https://gitlab.freedesktop.org/mesa/mesa/-/blob/e9169881dbd1f72eab65a68c2b8e7643f74489b7/meson_options.txt#L708)| i915and xe KMDs can be supported at the same time. |
249
+
| Compute | Default | NEO_ENABLE_I915_PRELIM_DETECTION | Default since `24.13.29138.x` | Same-time support can be built for all three KMDs. |
250
+
| Media | Default | ENABLE_PRODUCTION_KMD | Default since `intel-media-25.2.2` | `xe` with either upstream or out-of-tree `i915`, not all three. |
251
+
| Graphics | Default | Unsupported | Default since `mesa-24.0.5` | Both `i915` (upsteam) and `xe` KMDs supported at the same time. |
0 commit comments