Lines Matching +full:gitlab +full:- +full:ci
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.
61 which needs to be demonstrated by CI results.
70 Xe – Pre-Merge Goals - Work-in-Progress
74 -----------------------------
80 that display can already be part of the initial pull request towards drm-next.
84 from the first pull request of Xe towards drm-next. The expectation is that when
85 both drivers are part of the drm-tip, the introduction of cleaner patches will be
93 Xe – Pre-Merge Goals - Completed
97 --------
105 This item ties into the GPUVA, VM_BIND, and even long-running compute support.
111 -------------------------------
129 * Locking, including the page-faulting case.
133 The document is now included in the drm documentation :doc:`here </gpu/drm-vm-bind-async>`.
143 -------------
152 :doc:`The ASYNC VM_BIND document </gpu/drm-vm-bind-async>`.
155 -------------
158 resolve syncobj and dma-buf implicit sync dependencies. However, drm_scheduler is
159 not yet prepared to handle the 1-to-1 relationship between drm_gpu_scheduler and
169 through drm-misc. This, by itself, already includes the reach of an agreement for
173 --------------------------------------------------------
175 contexts, with the minimal scaffolding for preempt-ctx fences (probably on the
179 The goal is to achieve a consensus ahead of Xe initial pull-request, ideally with
180 this minimal drm/scheduler work, if needed, merged to drm-misc in a way that any
181 drm driver, including Xe, could re-use and add their own individual needs on top
185 ------------
196 Later, when we are in-tree, the goal is to collaborate with devcoredump
202 -----------
219 ------
233 related patch should be independent and present on dri-devel or acked by
234 maintainers to go along with the first Xe pull request towards drm-next.