Print this page
4630 clean stale references to ddi_iopb_alloc and ddi_iopb_free
4634 undocument scsi_hba_attach() and ddi_dma_lim(9s)
*** 1217,1228 ****
* the object that any cached references to the object are
* now stale (and flush or invalidate these stale cache references
* as necessary).
*
* The function ddi_dma_sync() provides the general interface with
! * respect to this capability. Generally, ddi_dma_free() (below) may
! * be used in preference to ddi_dma_sync() as ddi_dma_free() calls
* ddi_dma_sync().
*
* Returns 0 if all caches that exist and are specified by cache_flags
* are successfully operated on, else -1.
*
--- 1217,1228 ----
* the object that any cached references to the object are
* now stale (and flush or invalidate these stale cache references
* as necessary).
*
* The function ddi_dma_sync() provides the general interface with
! * respect to this capability. Generally, ddi_dma_unbind_handle()
! * (below) may be used in preference to ddi_dma_sync() as it calls
* ddi_dma_sync().
*
* Returns 0 if all caches that exist and are specified by cache_flags
* are successfully operated on, else -1.
*
*** 1243,1253 ****
* Inquiring minds want to know when ddi_dma_sync should be used:
*
* + When an object is mapped for dma, assume that an
* implicit ddi_dma_sync() is done for you.
*
! * + When an object is unmapped (ddi_dma_free()), assume
* that an implicit ddi_dma_sync() is done for you.
*
* + At any time between the two times above that the
* memory object may have been modified by either
* the DMA device or a processor and you wish that
--- 1243,1253 ----
* Inquiring minds want to know when ddi_dma_sync should be used:
*
* + When an object is mapped for dma, assume that an
* implicit ddi_dma_sync() is done for you.
*
! * + When an object is unmapped (ddi_dma_unbind_handle()), assume
* that an implicit ddi_dma_sync() is done for you.
*
* + At any time between the two times above that the
* memory object may have been modified by either
* the DMA device or a processor and you wish that