diff options
author | Rodrigo Vivi <rodrigo.vivi@intel.com> | 2023-12-01 07:21:55 +0300 |
---|---|---|
committer | Rodrigo Vivi <rodrigo.vivi@intel.com> | 2023-12-07 19:01:12 +0300 |
commit | aa15b031854fc86fd0b9c7e6b794d57563cba60f (patch) | |
tree | b6a70f97dc72f0e0d455331655a4f1fc1d07b93f | |
parent | 34e64dd192071c3159c118331f87c66dffa0f9c9 (diff) | |
download | linux-aa15b031854fc86fd0b9c7e6b794d57563cba60f.tar.xz |
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: Rodrigo Vivi <rodrigo.vivi@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20231201042158.80009-6-rodrigo.vivi@intel.com
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
-rw-r--r-- | Documentation/gpu/rfc/xe.rst | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/Documentation/gpu/rfc/xe.rst b/Documentation/gpu/rfc/xe.rst index cfff8a59a876..97cf87578f97 100644 --- a/Documentation/gpu/rfc/xe.rst +++ b/Documentation/gpu/rfc/xe.rst @@ -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. |