mirror of
https://github.com/torvalds/linux.git
synced 2026-04-23 00:55:48 -04:00
d490ecf577
Replace the calls to ttm_eu_reserve_buffers() by using the drm_exec helper instead. Also make sure the locking loop covers any calls to xe_bo_validate() / ttm_bo_validate() so that these function calls may easily benefit from being called from within an unsealed locking transaction and may thus perform blocking dma_resv locks in the future. For the unlock we remove an assert that the vm->rebind_list is empty when locks are released. Since if the error path is hit with a partly locked list, that assert may no longer hold true we chose to remove it. v3: - Don't accept duplicate bo locks in the rebind worker. v5: - Loop over drm_exec objects in reverse when unlocking. v6: - We can't keep the WW ticket when retrying validation on OOM. Fix. Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com> Reviewed-by: Matthew Brost <matthew.brost@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230908091716.36984-5-thomas.hellstrom@linux.intel.com Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
74 lines
2.0 KiB
Plaintext
74 lines
2.0 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
config DRM_XE
|
|
tristate "Intel Xe Graphics"
|
|
depends on DRM && PCI && MMU
|
|
select INTERVAL_TREE
|
|
# we need shmfs for the swappable backing store, and in particular
|
|
# the shmem_readpage() which depends upon tmpfs
|
|
select SHMEM
|
|
select TMPFS
|
|
select DRM_BUDDY
|
|
select DRM_EXEC
|
|
select DRM_KMS_HELPER
|
|
select DRM_PANEL
|
|
select DRM_SUBALLOC_HELPER
|
|
select RELAY
|
|
select IRQ_WORK
|
|
select SYNC_FILE
|
|
select IOSF_MBI
|
|
select CRC32
|
|
select SND_HDA_I915 if SND_HDA_CORE
|
|
select CEC_CORE if CEC_NOTIFIER
|
|
select VMAP_PFN
|
|
select DRM_TTM
|
|
select DRM_TTM_HELPER
|
|
select DRM_EXEC
|
|
select DRM_GPUVM
|
|
select DRM_SCHED
|
|
select MMU_NOTIFIER
|
|
select WANT_DEV_COREDUMP
|
|
help
|
|
Experimental driver for Intel Xe series GPUs
|
|
|
|
If "M" is selected, the module will be called xe.
|
|
|
|
config DRM_XE_FORCE_PROBE
|
|
string "Force probe xe for selected Intel hardware IDs"
|
|
depends on DRM_XE
|
|
help
|
|
This is the default value for the xe.force_probe module
|
|
parameter. Using the module parameter overrides this option.
|
|
|
|
Force probe the xe for Intel graphics devices that are
|
|
recognized but not properly supported by this kernel version. It is
|
|
recommended to upgrade to a kernel version with proper support as soon
|
|
as it is available.
|
|
|
|
It can also be used to block the probe of recognized and fully
|
|
supported devices.
|
|
|
|
Use "" to disable force probe. If in doubt, use this.
|
|
|
|
Use "<pci-id>[,<pci-id>,...]" to force probe the xe for listed
|
|
devices. For example, "4500" or "4500,4571".
|
|
|
|
Use "*" to force probe the driver for all known devices.
|
|
|
|
Use "!" right before the ID to block the probe of the device. For
|
|
example, "4500,!4571" forces the probe of 4500 and blocks the probe of
|
|
4571.
|
|
|
|
Use "!*" to block the probe of the driver for all known devices.
|
|
|
|
menu "drm/Xe Debugging"
|
|
depends on DRM_XE
|
|
depends on EXPERT
|
|
source "drivers/gpu/drm/xe/Kconfig.debug"
|
|
endmenu
|
|
|
|
menu "drm/xe Profile Guided Optimisation"
|
|
visible if EXPERT
|
|
depends on DRM_XE
|
|
source "drivers/gpu/drm/xe/Kconfig.profile"
|
|
endmenu
|