lkml.org 
[lkml]   [2022]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH v5 07/14] PCI: Add driver dma ownership management
    From
    On 2/14/22 9:43 PM, Jason Gunthorpe wrote:
    > On Mon, Feb 14, 2022 at 02:39:18PM +0100, Greg Kroah-Hartman wrote:
    >
    >>> A driver that sets this flag can still decide to enable the dma API on
    >>> its own. eg tegra drivers do this.
    >>
    >> So you are just forcing the driver to manage this all on their own, so
    >> how about, "driver_managed_dma", or even shorter "managed_dma"?
    >
    > Yeah, I like "driver_managed_dma" alot, it captures the entire idea

    This makes a lot of sense. For most drivers, they don't need to care
    about this flag as all DMAs are handled through the kernel DMA API. For
    VFIO or similar drivers, they know how to manage the DMA themselves and
    set this flag so that the IOMMU layer will allow them to setup and
    manage their own I/O address space.

    If there is no better naming, I'd like to use this and add some comments
    for device drivers developers.

    Thanks a lot to Greg and Jason.

    Best regards,
    baolu

    \
     
     \ /
      Last update: 2022-02-15 04:08    [W:2.514 / U:0.056 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site