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)

Split Close
Expand all
Collapse all
          --- old/usr/src/uts/common/sys/ddidmareq.h
          +++ new/usr/src/uts/common/sys/ddidmareq.h
↓ open down ↓ 683 lines elided ↑ open up ↑
 684  684   * mapped by the DMA handle up to date. It should be used by a
 685  685   * driver after a cpu modifies the memory object (over the range
 686  686   * specified by the other arguments to the ddi_dma_sync(9F) call).
 687  687   *
 688  688   * DDI_DMA_SYNC_FORCPU makes all cpu references to the object
 689  689   * mapped by the DMA handle up to date. It should be used
 690  690   * by a driver after the receipt of data from the device to
 691  691   * the memory object is done (over the range specified by
 692  692   * the other arguments to the ddi_dma_sync(9F) call).
 693  693   *
 694      - * If the only mapping that concerns the driver is one for the
 695      - * kernel (such as memory allocated by ddi_iopb_alloc(9F)), the
 696      - * flag DDI_DMA_SYNC_FORKERNEL can be used. This is a hint to the
      694 + * If the only mapping that concerns the driver is one for the kernel,
      695 + * the flag DDI_DMA_SYNC_FORKERNEL can be used. This is a hint to the
 697  696   * system that if it can synchronize the kernel's view faster
 698  697   * that the CPU's view, it can do so, otherwise it acts the
 699  698   * same as DDI_DMA_SYNC_FORCPU. DDI_DMA_SYNC_FORKERNEL might
 700  699   * speed up the synchronization of kernel mappings in case of
 701  700   * non IO-coherent CPU caches.
 702  701   */
 703  702  #define DDI_DMA_SYNC_FORDEV     0x0
 704  703  #define DDI_DMA_SYNC_FORCPU     0x1
 705  704  #define DDI_DMA_SYNC_FORKERNEL  0x2
 706  705  
↓ open down ↓ 99 lines elided ↑ open up ↑
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX