[lkml]   [2012]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [Linaro-mm-sig] [PATCH 2/3] dma-buf: add support for kernel cpu access
    On Fri, Mar 2, 2012 at 23:53, Rob Clark <> wrote:
    > nitially the expectation was that userspace would not pass a buffer
    > to multiple subsystems for writing (or that if it did, it would get
    > the undefined results that one could expect)..  so dealing w/
    > synchronization was punted.

    Imo synchronization should not be part of the dma_buf core, i.e.
    userspace needs to ensure that access is synchronized.
    begin/end_cpu_access are the coherency brackets (like map/unmap for
    device dma). And if userspace asks for a gun and some bullets, the
    kernel should just deliver. Even in drm/i915 gem land we don't (and
    simply can't) make any promises about concurrent reads/writes/ioctls.

    > I expect, though, that one of the next steps is some sort of
    > sync-object mechanism to supplement dmabuf

    Imo the only reason to add sync objects as explicit things is to make
    device-to-device sync more efficient by using hw semaphores and
    signalling lines. Or maybe a quick irq handler in the kernel that
    kicks of the next device. I don't think we should design these to make
    userspace simpler.

    Cheers, Daniel
    Daniel Vetter - +41 (0) 79 365 57 48 -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2012-03-05 22:35    [W:0.284 / U:31.608 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site