Lines Matching refs:CCB

34 (CCB). The CCB contains an opcode and various parameters. The opcode
36 options, flags, sizes, and addresses.  The CCB (or an array of CCBs)
40 there was an error.  One of the addresses given in each CCB is a
70 request can be fed to the coprocessor, all the addresses in a CCB must
72 it has no visibility into physical addresses. So a CCB may contain
75 may be given in the CCB. In all cases, the Hypervisor will translate
124 Kills a CCB during execution. The CCB is guaranteed to not continue
131 Retrieves information about a currently executing CCB. Note that some
132 Hypervisors might return 'notfound' when the CCB is in 'inprogress'
133 state. To ensure a CCB in the 'notfound' state will never be executed,
134 CCB_KILL must be invoked on that CCB. Upon success, read() must be
140 A write() whose length is a multiple of the CCB size is treated as a
148 should not subsequently call read(). Partial acceptance of the CCB
151 status will reflect the error caused by the first CCB that was not
186  - allocate a CCB and fill in the opcode, flags, parameters, addresses, etc.
187  - submit CCB via write() or pwrite()
205 The Hypervisor translates all addresses within a CCB to physical
206 before handing off the CCB to DAX. The Hypervisor determines the
232 CCB Structure
234 A CCB is an array of 8 64-bit words. Several of these words provide
254  - CCB version, which must be consistent with hardware version
266 provided by the driver. The setup of the CCB is nearly identical for
303 For details of all the parameters and bits used in this CCB, please
307 	ccb->control =       /* Table 36.1, CCB Header Format */
311 		             /* Section 36.2.1, Query CCB Command Formats */
334 The CCB submission is a write() or pwrite() system call to the
344 After a successful submission of the CCB, the completion area may be
363 CCB and validity of the output bitmap, which may be used immediately.
392 type must be given in the CCB::
394 	ccb->control |=      /* Table 36.1, CCB Header Format */