My understanding is that it is possible to manually trigger the binding (by adding eg. i915.force_probe=!56a0 xe.force_probe=56a0 as kernel parameters). Would the fact that its does not bind to hardware by default not mitigate the experimentalness somewhat?
In case you are not aware, there are other major distros is already including it - see below for example for Ubuntu 24.04 LTS where it was enabled for kernel 6.8:
~$ lsb_release -d
No LSB modules are available.
Description: Ubuntu 24.04.1 LTS
~$ lsmod | grep xe
xe 2707456 0
drm_gpuvm 45056 1 xe
drm_exec 12288 2 drm_gpuvm,xe
gpu_sched 61440 1 xe
drm_suballoc_helper 16384 1 xe
drm_ttm_helper 12288 1 xe
drm_buddy 20480 2 xe,i915
ttm 110592 3 drm_ttm_helper,xe,i915
drm_display_helper 237568 2 xe,i915
cec 94208 3 drm_display_helper,xe,i915
i2c_algo_bit 16384 2 xe,i915
video 73728 2 xe,i915
~$ uname -a
Linux scorcher 6.8.0-44-generic #44-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 13 13:35:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
~$ grep CONFIG_DRM_XE /boot/config-6.8.0-44-generic
CONFIG_DRM_XE=m
CONFIG_DRM_XE_DISPLAY=y
CONFIG_DRM_XE_FORCE_PROBE=""
# CONFIG_DRM_XE_WERROR is not set
# CONFIG_DRM_XE_DEBUG is not set
# CONFIG_DRM_XE_DEBUG_VM is not set
# CONFIG_DRM_XE_DEBUG_SRIOV is not set
# CONFIG_DRM_XE_DEBUG_MEM is not set
# CONFIG_DRM_XE_SIMPLE_ERROR_CAPTURE is not set
# CONFIG_DRM_XE_LARGE_GUC_BUFFER is not set
# CONFIG_DRM_XE_USERPTR_INVAL_INJECT is not set
CONFIG_DRM_XE_JOB_TIMEOUT_MAX=10000
CONFIG_DRM_XE_JOB_TIMEOUT_MIN=1
CONFIG_DRM_XE_TIMESLICE_MAX=10000000
CONFIG_DRM_XE_TIMESLICE_MIN=1
CONFIG_DRM_XE_PREEMPT_TIMEOUT=640000
CONFIG_DRM_XE_PREEMPT_TIMEOUT_MAX=10000000
CONFIG_DRM_XE_PREEMPT_TIMEOUT_MIN=1
CONFIG_DRM_XE_ENABLE_SCHEDTIMEOUT_LIMIT=y