Commit aa15b031 authored by Rodrigo Vivi's avatar Rodrigo Vivi
Browse files

drm/doc/rfc: Xe is using drm_exec, so mark as completed 



Nothing else to be done on this front from Xe perspective.

Signed-off-by: default avatarRodrigo Vivi <rodrigo.vivi@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20231201042158.80009-6-rodrigo.vivi@intel.com


Acked-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
parent 34e64dd1

Documentation/gpu/rfc/xe.rst

+8 −8
Original line number Diff line number Diff line
@@ -85,6 +85,14 @@ from the first pull request of Xe towards drm-next. The expectation is that when 
both drivers are part of the drm-tip, the introduction of cleaner patches will be

easier and speed up.



Xe – uAPI high level overview

=============================



...Warning: To be done in follow up patches after/when/where the main consensus in various items are individually reached.



Xe – Pre-Merge Goals - Completed

================================



Drm_exec

--------

Helper to make dma_resv locking for a big number of buffers is getting removed in
@@ -99,14 +107,6 @@ This item ties into the GPUVA, VM_BIND, and even long-running compute support. 
As a key measurable result, we need to have a community consensus documented in

this document and the Xe driver prepared for the changes, if necessary.



Xe – uAPI high level overview

=============================



...Warning: To be done in follow up patches after/when/where the main consensus in various items are individually reached.



Xe – Pre-Merge Goals - Completed

================================



Userptr integration and vm_bind

-------------------------------

Different drivers implement different ways of dealing with execution of userptr.