mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-03 09:29:42 +00:00
ece91c882d
VM_BIND design document with description of intended use cases.
v2: Reduce the scope to simple Mesa use case.
v3: Expand documentation on dma-resv usage, TLB flushing and
execbuf3.
v4: Remove vm_bind tlb flush request support.
v5: Update TLB flushing documentation.
v6: Update out of order completion documentation.
Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Acked-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220701003110.24843-2-niranjana.vishwanathapura@intel.com
33 lines
840 B
ReStructuredText
33 lines
840 B
ReStructuredText
===============
|
|
GPU RFC Section
|
|
===============
|
|
|
|
For complex work, especially new uapi, it is often good to nail the high level
|
|
design issues before getting lost in the code details. This section is meant to
|
|
host such documentation:
|
|
|
|
* Each RFC should be a section in this file, explaining the goal and main design
|
|
considerations. Especially for uapi make sure you Cc: all relevant project
|
|
mailing lists and involved people outside of dri-devel.
|
|
|
|
* For uapi structures add a file to this directory with and then pull the
|
|
kerneldoc in like with real uapi headers.
|
|
|
|
* Once the code has landed move all the documentation to the right places in
|
|
the main core, helper or driver sections.
|
|
|
|
.. toctree::
|
|
|
|
i915_gem_lmem.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_scheduler.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_small_bar.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_vm_bind.rst
|