On Fri, Jun 10, 2022 at 12:07:08AM -0700, Niranjana Vishwanathapura wrote:
This is the i915 driver VM_BIND feature design RFC patch series along with the required uapi definition and description of intended use cases.
Some of us had an offline dicussion on this. Based on that, 1) The scope of this work (VM_BIND support in i915) will reduced to support simple Mesa use case. So, I will remove all compute related uapi for now. 2) VM_BIND/UNBIND will only support an 'out' fence. ie., it won't support 'in' fences and hence no timeline fence array as well. UMDs are expected to handle any 'in' fence requirement. 3) We will not support any VM_BIND/UNBIND queues. The binding and unbinding operations can get completed out of submission order. Normally, they will get completed synchronously, but if the object is being moved, the binding will happen once that is complete and out fence will be signaled after binding is complete. 4) We will still have execbuf3 for VM_BIND mode. I will update the patch series and send out. Thanks, Niranjana
This series is an updated version of the below RFC series. It address the review feedback by adding execbuf3 ioctl for vm_bind, adding multiple queues support for vm_bind/unbind ioctls and some formatting and documentation updates. https://www.spinics.net/lists/dri-devel/msg347731.html Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@xxxxxxxxx> Niranjana Vishwanathapura (3): drm/doc/rfc: VM_BIND feature design document drm/i915: Update i915 uapi documentation drm/doc/rfc: VM_BIND uapi definition Documentation/driver-api/dma-buf.rst | 2 + Documentation/gpu/rfc/i915_vm_bind.h | 490 +++++++++++++++++++++++++ Documentation/gpu/rfc/i915_vm_bind.rst | 309 ++++++++++++++++ Documentation/gpu/rfc/index.rst | 4 + include/uapi/drm/i915_drm.h | 203 +++++++--- 5 files changed, 963 insertions(+), 45 deletions(-) create mode 100644 Documentation/gpu/rfc/i915_vm_bind.h create mode 100644 Documentation/gpu/rfc/i915_vm_bind.rst -- 2.21.0.rc0.32.g243a4c7e27
