Fix spelling error for 'parallel'Signed-off-by: Anish Dabhane <anishdabhane71@gmail.com>Signed-off-by: Jonathan Corbet <corbet@lwn.net>Message-ID: <20250518140107.21310-1-anishdabhane71@gmail.com>
drm/gpusvm: Fix kernel-docDue to wrong `.. kernel-doc` directive in Documentation/gpu/rfc/gpusvm.rstthe documentation was actually not parsing anything fromdrivers/gpu/drm/drm_gpusvm.c. This fixe
drm/gpusvm: Fix kernel-docDue to wrong `.. kernel-doc` directive in Documentation/gpu/rfc/gpusvm.rstthe documentation was actually not parsing anything fromdrivers/gpu/drm/drm_gpusvm.c. This fixes the kernel-doc include and allwarnings/errors created when doing so.Cc: Simona Vetter <simona.vetter@ffwll.ch>Cc: Dave Airlie <airlied@redhat.com>Cc: Christian König <christian.koenig@amd.com>Cc: dri-devel@lists.freedesktop.orgCc: Matthew Brost <matthew.brost@intel.com>Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>Closes: https://lore.kernel.org/intel-xe/20250307195239.57abcd2d@canb.auug.org.au/Fixes: 99624bdff867 ("drm/gpusvm: Add support for GPU Shared Virtual Memory")Reviewed-by: Matthew Brost <matthew.brost@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20250307-fix-svm-kerneldoc-v2-1-03c74b199620@intel.comSigned-off-by: Lucas De Marchi <lucas.demarchi@intel.com>(cherry picked from commit 4da1fb61e02a783fdd7eb725ea03d897b8ef19ea)Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
show more ...
drm/doc: gpusvm: Add GPU SVM documentationAdd documentation for agree upon GPU SVM design principles, currentstatus, and future plans.v4: - Address Thomas's feedbackv5: - s/Current/Basline (T
drm/doc: gpusvm: Add GPU SVM documentationAdd documentation for agree upon GPU SVM design principles, currentstatus, and future plans.v4: - Address Thomas's feedbackv5: - 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
drm/i915: Drop dead code for xehpsdvPCI IDs for XEHPSDV were never added and platform always marked withforce_probe. Drop what's not used and rename some places to either bexehp or dg2, depending
drm/i915: Drop dead code for xehpsdvPCI IDs for XEHPSDV were never added and platform always marked withforce_probe. Drop what's not used and rename some places to either bexehp or dg2, depending on the platform/IP checks.The registers not used anymore are also removed.Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Acked-by: Tvrtko Ursulin <tursulin@ursulin.net>Link: https://patchwork.freedesktop.org/patch/msgid/20240320060543.4034215-2-lucas.demarchi@intel.comSigned-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
drm/doc/rfc: Removing missing reference to xe.rstThe file has already been deleted as the tasks were completed.However the index reference was missed behind.fixes a doc build warning:Documenta
drm/doc/rfc: Removing missing reference to xe.rstThe file has already been deleted as the tasks were completed.However the index reference was missed behind.fixes a doc build warning:Documentation/gpu/rfc/index.rst:35: WARNING: toctree containsreference to nonexisting document 'gpu/rfc/xe'Fixes: d11dc7aa98e5 ("drm/doc/rfc: Remove Xe's pre-merge plan")Cc: Lucas De Marchi <lucas.demarchi@intel.com>Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Reviewed-by: Matthew Auld <matthew.auld@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20240116220331.145607-1-rodrigo.vivi@intel.com
drm/doc/rfc: Remove Xe's pre-merge planThe last TODO item here that was not marked as done wasthe display portion, which came along with the pull-request.So, now that Xe is part of drm-next and
drm/doc/rfc: Remove Xe's pre-merge planThe last TODO item here that was not marked as done wasthe display portion, which came along with the pull-request.So, now that Xe is part of drm-next and it includes thedisplay portion, let's entirely kill this RFC here.Cc: Lucas De Marchi <lucas.demarchi@intel.com>Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>Cc: Oded Gabbay <ogabbay@kernel.org>Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20240110190427.63095-1-rodrigo.vivi@intel.comAcked-by: Lucas De Marchi <lucas.demarchi@intel.com>
drm/doc/rfc: Xe is using drm_exec, so mark as completedNothing else to be done on this front from Xe perspective.Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Link: https://patchwork.freed
drm/doc/rfc: Xe is using drm_exec, so mark as completedNothing 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.comAcked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drm/doc/rfc: Move userptr integration and vm_bind to the 'completed' sectionThe must-have part of the documentation was already added to the existing/gpu/drm-vm-bind-async. The other extra discuss
drm/doc/rfc: Move userptr integration and vm_bind to the 'completed' sectionThe must-have part of the documentation was already added to the existing/gpu/drm-vm-bind-async. The other extra discussion around GPUVM helpersare currently active in the community. None of those discussion shouldblock Xe since documentation, specially around locking was completed ina community consensus.Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20231201042158.80009-5-rodrigo.vivi@intel.comAcked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drm/doc/rfc: Move Xe 'ASYNC VM_BIND' to the 'completed' sectionAs already indicated in this block, the consensus was alreadyreached out and documented as:The ASYNC VM_BIND document </gpu/drm-vm-b
drm/doc/rfc: Move Xe 'ASYNC VM_BIND' to the 'completed' sectionAs already indicated in this block, the consensus was alreadyreached out and documented as:The ASYNC VM_BIND document </gpu/drm-vm-bind-async>However this was item was not moved to the completed section.Let's move and clean up the WIP block.Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20231201042158.80009-4-rodrigo.vivi@intel.comAcked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drm/doc/rfc: Mark drm_scheduler as completedCurrent drm-xe-next doesn't have any drm/scheduler patch that is notalready accepted in drm-misc-next. This completed this goal withthe consensus of ho
drm/doc/rfc: Mark drm_scheduler as completedCurrent drm-xe-next doesn't have any drm/scheduler patch that is notalready accepted in drm-misc-next. This completed this goal withthe consensus of how the drm/scheduler fits to the fw scheduling andthe relationship between drm_gpu_scheduler and drm_sched_entity.Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20231201042158.80009-3-rodrigo.vivi@intel.comAcked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drm/doc/rfc: Mark long running workload as complete.No DRM scheduler changes required, drivers just return NULL in run_jobvfunc.The rough consensus is that no helper or extra scaffolding is need
drm/doc/rfc: Mark long running workload as complete.No DRM scheduler changes required, drivers just return NULL in run_jobvfunc.The rough consensus is that no helper or extra scaffolding is neededaround long-running jobs and no further changes to drm-scheduler.At least for now. Other drivers that currently do long-running workloadshave no plat to use drm-scheduler. Besides, the current consensus isthat this solution of simply returning NULL to the run_job function shouldwork without extra code duplication or complication.On top of that, this item was already a non-blocking one for upstreaming Xe,so let's move that to the 'Completed' section and revisit the long-runningsolution as a community after Xe is integrated in DRM.Signed-off-by: Matthew Brost <matthew.brost@intel.com>Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20231201042158.80009-2-rodrigo.vivi@intel.comAcked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Documentation/gpu: VM_BIND locking documentAdd the first version of the VM_BIND locking document which isintended to be part of the xe driver upstreaming agreement.The document describes and dis
Documentation/gpu: VM_BIND locking documentAdd the first version of the VM_BIND locking document which isintended to be part of the xe driver upstreaming agreement.The document describes and discuss the locking used during exec-functions, evicton and for userptr gpu-vmas. Intention is to be using thesame nomenclature as the drm-vm-bind-async.rst.v2:- s/gvm/gpu_vm/g (Rodrigo Vivi)- Clarify the userptr seqlock with a pointer to mm/mmu_notifier.c (Rodrigo Vivi)- Adjust commit message accordingly.- Add SPDX license header.v3:- Large update to align with the drm_gpuvm manager locking- Add "Efficient userptr gpu_vma exec function iteration" section- Add "Locking at bind- and unbind time" section.v4:- Fix tabs vs space errors by untabifying (Rodrigo Vivi)- Minor style fixes and typos (Rodrigo Vivi)- Clarify situations where stale GPU mappings are occurring and how access through these mappings are blocked. (Rodrigo Vivi)- Insert into the toctree in implementation_guidelines.rstv5:- Add a section about recoverable page-faults.- Use local references to other documentation where possible (Bagas Sanjaya)- General documentation fixes and typos (Danilo Krummrich and Boris Brezillon)- Improve the documentation around locks that need to be grabbed from the dm-fence critical section (Boris Brezillon)- Add more references to the DRM GPUVM helpers (Danilo Krummrich and Boriz Brezillon)- Update the rfc/xe.rst document.v6:- Rework wording to improve readability (Boris Brezillon, Rodrigo Vivi, Bagas Sanjaya)- Various minor fixes across the document (Boris Brezillon)Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Reviewed-by: Danilo Krummrich <dakr@redhat.com>Acked-by: John Hubbard <jhubbard@nvidia.com> # Documentation/core-api/pin_user_pages.rst changesLink: https://patchwork.freedesktop.org/patch/msgid/20231129090637.2629-1-thomas.hellstrom@linux.intel.com
Documentation/gpu: Add a VM_BIND async documentAdd a motivation for and description of asynchronous VM_BIND operationv2:- Fix typos (Nirmoy Das)- Improve the description of a memory fence (Oak
Documentation/gpu: Add a VM_BIND async documentAdd a motivation for and description of asynchronous VM_BIND operationv2:- Fix typos (Nirmoy Das)- Improve the description of a memory fence (Oak Zeng)- Add a reference to the document in the Xe RFC.- Add pointers to sample uAPI suggestionsv3:- Address review comments (Danilo Krummrich)- Formatting fixesv4:- Address typos (Francois Dugast)- Explain why in-fences are not allowed for VM_BIND operations for long- running workloads (Matthew Brost)v5:- More typo- and style fixing- Further clarify the implications of disallowing in-fences for VM_BIND operations for long-running workloads (Matthew Brost)v6:- Point out that a gpu_vm is a virtual GPU Address space. (Danilo Krummrich)- For an explanation of dma-fences point to the dma-fence documentation. (Paulo Zanoni)- Clarify that VM_BIND errors are reported synchronously. (Paulo Zanoni)- Use an rst doc reference when pointing to the async vm_bind document from the xe merge plan.- Add the VM_BIND documentation to the drm documentation table-of-content, using an intermediate "Misc DRM driver uAPI- and feature implementation guidelines"v7:- Update the error handling documentation to remove the VM error state.v8:- Clarify error handling and difference in operation support between async VM_BIND and sync VM_BIND. (Paulo Zanoni)- Update the sample uAPI with a self-contained example. (Paulo Zanoni)Cc: Paulo R Zanoni <paulo.r.zanoni@intel.com>Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>Acked-by: Nirmoy Das <nirmoy.das@intel.com>Reviewed-by: Danilo Krummrich <dakr@redhat.com>Reviewed-by: Matthew Brost <matthew.brost@intel.com>Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20231012132552.20196-1-thomas.hellstrom@linux.intel.com
Merge tag 'drm-misc-next-2023-09-11-1' of git://anongit.freedesktop.org/drm/drm-misc into drm-nextdrm-misc-next for v6.7-rc1:UAPI Changes:- Nouveau changed to not set NO_PREFETCH flag explicitly
Merge tag 'drm-misc-next-2023-09-11-1' of git://anongit.freedesktop.org/drm/drm-misc into drm-nextdrm-misc-next for v6.7-rc1:UAPI Changes:- Nouveau changed to not set NO_PREFETCH flag explicitly.Cross-subsystem Changes:- Update documentation of dma-buf intro and uapi.- fbdev/sbus fixes.- Use initializer macros in a lot of fbdev drivers.- Add Boris Brezillon as Panfrost driver maintainer.- Add Jessica Zhang as drm/panel reviewer.- Make more fbdev drivers use fb_ops helpers for deferred io.- Small hid trailing whitespace fix.- Use fb_ops in hid/picolcdCore Changes:- Assorted small fixes to ttm tests, drm/mst.- Documentation updates to bridge.- Add kunit tests for some drm_fb functions.- Rework drm_debugfs implementation.- Update xe documentation to mark todos as completed.Driver Changes:- Add support to rockchip for rv1126 mipi-dsi and vop.- Assorted small fixes to nouveau, bridge/samsung-dsim, bridge/lvds-codec, loongson, rockchip, panfrost, gma500, repaper, komeda, virtio, ssd130x.- Add support for simple panels Mitsubishi AA084XE01, JDI LPM102A188A,- Documentation updates to accel/ivpu.- Some nouveau scheduling/fence fixes.- Power management related fixes and other fixes to ivpu.- Assorted bridge/it66121 fixes.- Make platform drivers return void in remove() callback.Signed-off-by: Dave Airlie <airlied@redhat.com>From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/3da6554b-3b47-fe7d-c4ea-21f4f819dbb6@linux.intel.com
drm/doc/rfc: Mark GPU VA as complete.Nouveau has landed the GPU VA helpers, support and documentationalready and Xe is already using the upstream GPU VA.Link: https://gitlab.freedesktop.org/drm/
drm/doc/rfc: Mark GPU VA as complete.Nouveau has landed the GPU VA helpers, support and documentationalready and Xe is already using the upstream GPU VA.Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/commit/ea4ae69e66b2940107e74f240ecb9dae87bf1ff1Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/commits/drm-xe-next?ref_type=headsSigned-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>Acked-by: Danilo Krummrich <dakr@redhat.com>Link: https://patchwork.freedesktop.org/patch/msgid/20230829163005.54067-4-rodrigo.vivi@intel.com
drm/doc/rfc: Mark DRM_VM_BIND as complete.The consensus is for individual drivers VM_BIND uapis withthe GPUVA helpers that are already implemented and mergedupstream.The merged GPUVA documentat
drm/doc/rfc: Mark DRM_VM_BIND as complete.The consensus is for individual drivers VM_BIND uapis withthe GPUVA helpers that are already implemented and mergedupstream.The merged GPUVA documentation also establish some overallrules for the locking to be followed by the drivers.Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>Acked-by: Danilo Krummrich <dakr@redhat.com>Link: https://patchwork.freedesktop.org/patch/msgid/20230829163005.54067-3-rodrigo.vivi@intel.com
drm/doc/rfc: Mark Dev_coredump as completed.Xe is already using devcoredump infrastructure as the primaryerror state and all the changes needed for user space errorreplay and other useful logs ar
drm/doc/rfc: Mark Dev_coredump as completed.Xe is already using devcoredump infrastructure as the primaryerror state and all the changes needed for user space errorreplay and other useful logs are getting added into xe_devcoredump.Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/blob/drm-xe-next/drivers/gpu/drm/xe/xe_devcoredump.cSigned-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>Link: https://patchwork.freedesktop.org/patch/msgid/20230829163005.54067-2-rodrigo.vivi@intel.com
drm/doc/rfc: No STAGING out of drivers/staging.Also the uapi should be reviewed and scrutinized before xeis accepted upstream and we shouldn't cause regression.Link: https://lore.kernel.org/all/
drm/doc/rfc: No STAGING out of drivers/staging.Also the uapi should be reviewed and scrutinized before xeis accepted upstream and we shouldn't cause regression.Link: https://lore.kernel.org/all/20230630100059.122881-1-thomas.hellstrom@linux.intel.comAcked-by: Daniel Vetter <daniel.vetter@ffwll.ch>Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20230829163005.54067-1-rodrigo.vivi@intel.com
Merge tag 'docs-6.6' of git://git.lwn.net/linuxPull documentation updates from Jonathan Corbet: "Documentation work keeps chugging along; this includes: - Work from Carlos Bilbao to integrate
Merge tag 'docs-6.6' of git://git.lwn.net/linuxPull documentation updates from Jonathan Corbet: "Documentation work keeps chugging along; this includes: - Work from Carlos Bilbao to integrate rustdoc output into the generated HTML documentation. This took some work to figure out how to do it without slowing the docs build and without creating people who don't have Rust installed, but Carlos got there - Move the loongarch and mips architecture documentation under Documentation/arch/ - Some more maintainer documentation from Jakub ... plus the usual assortment of updates, translations, and fixes"* tag 'docs-6.6' of git://git.lwn.net/linux: (56 commits) Docu: genericirq.rst: fix irq-example input: docs: pxrc: remove reference to phoenix-sim Documentation: serial-console: Fix literal block marker docs/mm: remove references to hmm_mirror ops and clean typos docs/zh_CN: correct regi_chg(),regi_add() to region_chg(),region_add() Documentation: Fix typos Documentation/ABI: Fix typos scripts: kernel-doc: fix macro handling in enums scripts: kernel-doc: parse DEFINE_DMA_UNMAP_[ADDR|LEN] Documentation: riscv: Update boot image header since EFI stub is supported Documentation: riscv: Add early boot document Documentation: arm: Add bootargs to the table of added DT parameters docs: kernel-parameters: Refer to the correct bitmap function doc: update params of memhp_default_state= docs: Add book to process/kernel-docs.rst docs: sparse: fix invalid link addresses docs: vfs: clean up after the iterate() removal docs: Add a section on surveys to the researcher guidelines docs: move mips under arch docs: move loongarch under arch ...
Documentation: Fix typosFix typos in Documentation.Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>Link: https://lore.kernel.org/r/20230814212822.193684-4-helgaas@kernel.orgSigned-off-by: Jon
Documentation: Fix typosFix typos in Documentation.Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>Link: https://lore.kernel.org/r/20230814212822.193684-4-helgaas@kernel.orgSigned-off-by: Jonathan Corbet <corbet@lwn.net>
drm/doc: fix duplicate declaration warningWe have duplicate kernel-doc directives for the same struct, leading to:/home/jani/src/linux/Documentation/gpu/driver-uapi.rst:2279: WARNING: Duplicate C
drm/doc: fix duplicate declaration warningWe have duplicate kernel-doc directives for the same struct, leading to:/home/jani/src/linux/Documentation/gpu/driver-uapi.rst:2279: WARNING: Duplicate C declaration, also defined at rfc/i915_scheduler:3.Declaration is '.. c:struct:: i915_context_engines_parallel_submit'.Use the Sphinx C domain namespace for the rfc document to fix this.Signed-off-by: Jani Nikula <jani.nikula@intel.com>Reviewed-by: Luca Coelho <luciano.coelho@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20230621123156.14907-1-jani.nikula@intel.com
drm/doc/rfc: Introduce the merge plan for the Xe driver.Let’s establish a merge plan for Xe, by writing down clear pre-merge goals, inorder to avoid unnecessary delays.This initial document star
drm/doc/rfc: Introduce the merge plan for the Xe driver.Let’s establish a merge plan for Xe, by writing down clear pre-merge goals, inorder to avoid unnecessary delays.This initial document starts with a TODO list containing items with clear andmeasurable key results. Xe’s initial pull request should only be sent todri-devel after all the items are clearly resolved.Since many of them involve some level of a community consensus, in many cases,the consensus will be reached in follow-up patches to this document with moredetails of the API or helpers that will be developed or modified.Besides of the items that are highlighted in this document, it is importantto highlight that Oded, has been volunteered to give the overall ack on Xedriver as the way to confirm that it looks good for upstream.v2: Incorporated Daniel's feedback: - Do not make long-running compute a blocker. - Add a mention to drm-exec that that ties to vm_bind and long-running compute jobs. Then I also added GPUVA since I recently noticed that this ties also to the work Matt is doing on that front. - Added the devcoredump section. - Add the mention to Oded being volunteered for the overall ack.v3: Reword a bit the Async VM_BIND to incorporate Daniel's feedback on ensuring the async vmbind consensus explicitly include Mesa, besides other kernel drivers.Cc: Dave Airlie <airlied@redhat.com>Cc: Daniel Vetter <daniel.vetter@ffwll.ch>Cc: Oded Gabbay <ogabbay@kernel.org>Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>Signed-off-by: Francois Dugast <francois.dugast@intel.com>Signed-off-by: Luis Strano <luis.strano@intel.com>Signed-off-by: Matthew Brost <matthew.brost@intel.com>Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>Acked-by: Dave Airlie <airlied@redhat.com>Link: https://patchwork.freedesktop.org/patch/msgid/20230419191913.158807-1-rodrigo.vivi@intel.com
drm/doc/rfc: VM_BIND uapi definitionVM_BIND and related uapi definitionsv2: Reduce the scope to simple Mesa use case.v3: Expand VM_UNBIND documentation and add I915_GEM_VM_BIND/UNBIND_FENCE_
drm/doc/rfc: VM_BIND uapi definitionVM_BIND and related uapi definitionsv2: Reduce the scope to simple Mesa use case.v3: Expand VM_UNBIND documentation and add I915_GEM_VM_BIND/UNBIND_FENCE_VALID and I915_GEM_VM_BIND_TLB_FLUSH flags.v4: Remove I915_GEM_VM_BIND_TLB_FLUSH flag and add additional documentation for vm_bind/unbind.v5: Remove TLB flush requirement on VM_UNBIND. Add version support to stage implementation.v6: Define and use drm_i915_gem_timeline_fence structure for all timeline fences.v7: Rename I915_PARAM_HAS_VM_BIND to I915_PARAM_VM_BIND_VERSION. Update documentation on async vm_bind/unbind and versioning. Remove redundant vm_bind/unbind FENCE_VALID flag, execbuf3 batch_count field and I915_EXEC3_SECURE flag.v8: Remove I915_GEM_VM_BIND_READONLY and minor documentation updates.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-4-niranjana.vishwanathapura@intel.com
drm/doc/rfc: VM_BIND feature design documentVM_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
drm/doc/rfc: VM_BIND feature design documentVM_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
drm/doc: add rfc section for small BAR uapiAdd an entry for the new uapi needed for small BAR on DG2+.v2: - Some spelling fixes and other small tweaks. (Akeem & Thomas) - Rework error capture
drm/doc: add rfc section for small BAR uapiAdd an entry for the new uapi needed for small BAR on DG2+.v2: - Some spelling fixes and other small tweaks. (Akeem & Thomas) - Rework error capture interactions, including no longer needing NEEDS_CPU_ACCESS for objects marked for capture. (Thomas) - Add probed_cpu_visible_size. (Lionel)v3: - Drop the vma query for now. - Add unallocated_cpu_visible_size as part of the region query. - Improve the docs some more, including documenting the expected behaviour on older kernels, since this came up in some offline discussion.v4: - Various improvements all over. (Tvrtko)v5: - Include newer integrated platforms when applying the non-recoverable context and error capture restriction. (Thomas)Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16739Signed-off-by: Matthew Auld <matthew.auld@intel.com>Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>Cc: Jon Bloomfield <jon.bloomfield@intel.com>Cc: Daniel Vetter <daniel.vetter@ffwll.ch>Cc: Jordan Justen <jordan.l.justen@intel.com>Cc: Kenneth Graunke <kenneth@whitecape.org>Cc: Akeem G Abodunrin <akeem.g.abodunrin@intel.com>Cc: mesa-dev@lists.freedesktop.orgAcked-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>Acked-by: Akeem G Abodunrin <akeem.g.abodunrin@intel.com>Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>Acked-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>Acked-by: Jordan Justen <jordan.l.justen@intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20220629174350.384910-1-matthew.auld@intel.com
12