Lines Matching refs:operations
15 * ``VM_BIND``: An operation or a list of operations to modify a gpu_vm using
16 an IOCTL. The operations include mapping and unmapping system- or
57 operation. VM_BIND operations that use the same bind context can be
59 assumptions can be made for VM_BIND operations using separate bind contexts.
71 With Synchronous VM_BIND, the VM_BIND operations all complete before the
73 out-fences. Synchronous VM_BIND may block and wait for GPU operations;
79 IOCTL may return immediately, the VM_BIND operations wait for the in-syncobjs
88 If the VM_BIND IOCTL takes a list or an array of operations as an argument,
94 Since asynchronous VM_BIND operations may use dma-fences embedded in
109 operations for long-running workloads will not allow for pipelining
121 deeply pipelined behind other VM_BIND operations and workloads
126 created. For each context, VM_BIND operations will be guaranteed to
128 for VM_BIND operations executing on separate VM_BIND contexts. Instead
129 KMD will attempt to execute such VM_BIND operations in parallel but
138 the kernel mode driver to inject other operations into the bind /
139 unbind operations. Like for example inserting breakpoints into batch
144 There is no difference in the operations supported or in
150 The VM_BIND operations of the IOCTL may error for various reasons, for
163 Unbind operations are guaranteed not to return any errors due to
174 zero, one or many such operations. A zero number means only the
242 * operations, the BO handle MBZ, and the BO offset MBZ. This flag is
284 /** @flag: Flags controlling all operations in this ioctl. */