Current VM fault handling resolves PASIDs through VM state: PASID -> VM
Process-scoped event delivery paths such as EVENTFD notifications, debugger events, SQ messages and future WAIT_EVENT support may instead need to identify the owning DRM file-private object: PASID -> amdgpu_fpriv This RFC introduces a prototype PASID to fpriv lookup infrastructure for DRM file-private PASIDs. The existing PASID to VM mapping remains unchanged for VM fault handling, while this RFC adds a separate PASID to fpriv mapping for process-scoped event delivery. Architectural design discussion points: - Is PASID -> amdgpu_fpriv the correct routing direction for process-scoped events? - How should asynchronous users protect fpriv lifetime? Series is only compilation tested. Srinivasan Shanmugam (3): drm/amdgpu: Add PASID fpriv lookup manager drm/amdgpu: Register DRM fpriv PASID ownership drm/amdgpu: Add PASID to fpriv lookup helper drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 12 +++++ drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 60 +++++++++++++++++++++++++ drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 22 +++++++++ 3 files changed, 94 insertions(+) -- 2.34.1
