gpu/rfc/xe.rst

8 pre-merge goals, in order to avoid unnecessary delays.
29 As for the power management area, the goal is to have a much-simplified support
30 for the system suspend states (S-states), PCI device suspend states (D-states),
31 GPU/Render suspend states (R-states) and frequency management. It should leverage
32 as much as possible all the existent PCI-subsystem infrastructure (pm and
38 https://gitlab.freedesktop.org/drm/xe/kernel (branch drm-xe-next)
49 official and by-default probe at a given time.
76 Xe – Pre-Merge Goals
80 -------------
83 resolve syncobj and dma-buf implicit sync dependencies. However, drm_scheduler is
84 not yet prepared to handle the 1-to-1 relationship between drm_gpu_scheduler and
90 as the ARM’s new Mali GPU driver, and others.
93 depend on any other patch touching drm_scheduler itself that was not yet merged
94 through drm-misc. This, by itself, already includes the reach of an agreement for
98 ------
106 track of GPU virtual address mappings. This is still not merged upstream, but
112 related patch should be independent and present on dri-devel or acked by
113 maintainers to go along with the first Xe pull request towards drm-next.
116 -----------
127 Xe merged, it is mandatory to enforce the overall locking scheme for all major
133 -------------
135 Xe merged, it is mandatory to have a consensus with other drivers and Mesa.
145 -------------------------------
148 aim for a DRM consensus on what’s the best way to have that support. To some
163  * Locking, including the page-faulting case.
172 --------------------------------------------------------
174 contexts, with the minimal scaffolding for preempt-ctx fences (probably on the
178 The goal is to achieve a consensus ahead of Xe initial pull-request, ideally with
179 this minimal drm/scheduler work, if needed, merged to drm-misc in a way that any
180 drm driver, including Xe, could re-use and add their own individual needs on top
183 This is a non-blocker item since the driver without the support for the long
187 -----------------------------
193 that display can already be part of the initial pull request towards drm-next.
197 from the first pull request of Xe towards drm-next. The expectation is that when
198 both drivers are part of the drm-tip, the introduction of cleaner patches will be
202 --------
208 place waiting for Xe to get merged.
210 This item ties into the GPUVA, VM_BIND, and even long-running compute support.
216 ------------
227 Later, when we are in-tree, the goal is to collaborate with devcoredump