[0/5] Update xe.rst RFC doc

Message

Rodrigo Vivi Dec. 1, 2023, 4:21 a.m. UTC

Let's move more items from the 'WIP' section to the 'Completed' one.

When Xe was an initial experiment we had written down our goals and
promises in this RFC with the goal to work with and contribute back
to key common DRM items such as drm_scheduler, gpuvm, drm_exec, and
establish documentations and community consensus around other new items
like vm_bind async usage and its interaction with userptr and locking
primitives and rules, as well as long-running workloads with
drm_scheduler, etc. As well as other plans like devcoredump and i915
display re-usage.

We are so thankful for this great community and the great discussions,
reviews and cross contributions we got so far on this journey. Thank you
all.

Most of this checklist is already completed. We're finalizing some last
minute cleanups on the uAPI and will be sharing the first pull request
shortly.

Meanwhile, the Display team is also working to finalize the few remaining
patches to have a clean re-usage of i915 display. Please notice that this
is actually a formal item in this xe.rst RFC, but also it is a
non-blocking one.

Hopefully we will be able to align the Display for a common pull request.
But with the possibility of 2 separate pull requests, one right after the other.

We're looking forward to moving our work on Xe to the mainline and continuing
to evolve drm together towards a better future.

Matthew Brost (1):
  drm/doc/rfc: Mark long running workload as complete.

Rodrigo Vivi (4):
  drm/doc/rfc: Mark drm_scheduler as completed
  drm/doc/rfc: Move Xe 'ASYNC VM_BIND' to the 'completed' section
  drm/doc/rfc: Move userptr integration and vm_bind to the 'completed'
    section
  drm/doc/rfc: Xe is using drm_exec, so mark as completed

 Documentation/gpu/rfc/xe.rst | 127 +++++++++++++++++------------------
 1 file changed, 62 insertions(+), 65 deletions(-)