Lines Matching full:operation

15 * ``VM_BIND``: An operation or a list of operations to modify a gpu_vm using
24 * ``in-syncobj``: Argument to a VM_BIND IOCTL, the VM_BIND operation waits
27 * ``out-syncobj``: Argument to a VM_BIND_IOCTL, the VM_BIND operation
28 signals these when the bind operation is complete.
57 operation. VM_BIND operations that use the same bind context can be
66 Synchronous / Asynchronous VM_BIND operation
86 immediately available for preparing the asynchronous operation.
89 the in-syncobjs needs to signal before the first operation starts to
90 execute, and the out-syncobjs signal after the last operation
91 completes. Operations in the operation list can be assumed, where it
101 The purpose of an Asynchronous VM_BIND operation is for user-mode
104 operation is not allowed and any in-fences need to be awaited
107 VM_BIND operation will need to be awaited synchronously anyway (see
117 the VM_BIND operation only.
119 An asynchronous VM_BIND operation may take substantial time to
120 complete and signal the out_fence. In particular if the operation is
123 subsequent VM_BIND operation to be queued behind the first one if
145 multi-operation support between asynchronous VM_BIND and synchronous VM_BIND.
147 Multi-operation VM_BIND IOCTL error handling and interrupts
160 bind operation, due to an error return, no additional action is needed
161 to clean up the failed operation, and the VM is left in the same state
173 Starting with the VM_BIND operation struct, the IOCTL call can take
234 * Valid on a faulting VM only, do the MAP operation immediately rather
246 /** @op: Operation to perform (lower 16 bits) and flags (upper 16 bits) */