Lines Matching refs:status

26 …CCBs) via the ccb_submit API function. The operations are processed asynchronously, with the status
35 …recommended such implementation use the ccb_info API function to check the status of a CCB prior to
210 previous Serial CCB, regardless of the completion status of that CCB. The Conditional flag allows C…
909 …by the virtual machine, simply updates the completion area with its execution status. The CCB may …
980        0             1             CCB execution status
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 …ssfully. All other fields are considered invalid upon CCB submission until the CCB execution status
1029 CCBs which complete with status 0x2 or 0x3 may produce partial results and/or side effects due to p…
1032 completes with a status byte of 0x2, the error reason code byte can be read to determine what corre…
1094        ret0              status
1096        ret2              status data
1183 …first remaining CCB. Failure to do so will produce indeterminate CCB execution status and ordering.
1201 …The value of status data depends on the status value. See error status code descriptions for detai…
1202 …The value is undefined for status values that do not specifically list a value for the status data.
1236                translation is returned as status data in ret2. Some CCBs may have been
1250                which fails permission checking is returned as status data in ret2. Some
1254                submitted CCB, or may apply to a larger scope. The status should not be
1256                the future which had previously been unable to be performed. The status
1296         ret0                status
1302 …Requests status information on a previously submitted CCB. The previously submitted CCB is identif…
1356           ret0            status
1376 …                              will reflect the killed status, with the subsequent implications that
1396 …   target CCB may contain status (4,0) "Command was skipped" instead of (3,7) "Command was killed".
1398 …If the pipeline source CCB is killed, the pipeline target CCB's completion status may read (1,0) "…
1416           ret0             status