mirror of
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2025-08-05 16:54:27 +00:00

Add documentation for agree upon GPU SVM design principles, current status, and future plans. v4: - Address Thomas's feedback v5: - s/Current/Basline (Thomas) v7: - Add license (CI) - Add examples for design guideline reasoning (Alistair) - Add snippet about possible livelock with concurrent GPU and and CPU access (Alistair) Signed-off-by: Matthew Brost <matthew.brost@intel.com> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com> Acked-by: Alistair Popple <apopple@nvidia.com> Link: https://patchwork.freedesktop.org/patch/msgid/20250306012657.3505757-33-matthew.brost@intel.com
37 lines
870 B
ReStructuredText
37 lines
870 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::
|
|
|
|
gpusvm.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_gem_lmem.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_scheduler.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_small_bar.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_vm_bind.rst
|