Lines Matching refs:execution
28 …separate Completion Area and, unless execution order is specifically restricted through the use of…
29 …conditional flags, the execution order of submitted CCBs is arbitrary. Likewise, the time to compl…
131 referenced by a CCB must be pinned in memory until the CCB either completes execution or is killed
134 execution.
211 to conditionally execute based on the successful execution of the closest CCB marked with the Seria…
213 and Serial to allow execution chaining. The flags do NOT allow fan-out chaining, where multiple CCBs
541 minus 1. Command execution stops
544 minus 1. Command execution stops
549 minus 1. Command execution stops
909 …by the virtual machine, simply updates the completion area with its execution status. The CCB may …
912 … The sync command is a variant of the no-op command which with restricted execution timing. A sync
980 0 1 CCB execution status
985 … 0x3 Command ran and was killed (partial execution may
1003 0x8 Command execution timeout
1024 The CCB completion area should be treated as read-only by guest software. The CCB execution status
1025 byte will be cleared by the Hypervisor to reflect the pending execution status when the CCB is subm…
1026 successfully. All other fields are considered invalid upon CCB submission until the CCB execution s…
1030 execution of the CCB command. Some valid data may be accessible depending on the fault type, howeve…
1055 …Command kill indicates that the CCB execution was halted or prevented by use of the ccb_kill API c…
1057 …Command timeout indicates that the CCB execution began, but did not complete within a pre-determin…
1074 …The runtime field indicates the execution time of the CCB command once it leaves the internal virt…
1183 …first remaining CCB. Failure to do so will produce indeterminate CCB execution status and ordering.
1311 … ENQUEUED 1 The requested CCB is current in a queue awaiting execution.
1313 … be possible to stop the execution using the ccb_kill hypercall.
1359 …Request to stop execution of a previously submitted CCB. The previously submitted CCB is identifie…
1370 … never began execution, no memory modifications were produced by
1374 … request was submitted. The CCB execution was stopped, and the CCB
1385 … command execution if the command was stopped just prior to writing