Skip to content
Snippets Groups Projects
  1. Aug 11, 2012
  2. Aug 10, 2012
  3. Aug 09, 2012
  4. Aug 08, 2012
  5. Aug 06, 2012
  6. Aug 02, 2012
  7. Jul 23, 2012
  8. Jul 20, 2012
  9. Jul 19, 2012
  10. Jul 16, 2012
  11. Jul 13, 2012
    • Rob Clark's avatar
      omap: add refcnting and handle tracking · 22574aa8
      Rob Clark authored
      
      There can be scenarios, especially when re-importing an existing buffer,
      where you end up with multiple 'struct omap_bo's wrapping a single GEM
      object handle.  Which causes badness when the first of the evil-clones
      is omap_bo_del()'d.
      
      To do this, introduce reference counting and a hashtable to track the
      handles per fd.
      
      First, to avoid bo's slipping through the crack if multiple 'struct
      omap_device's are created for one drm fd, a hashtable mapping drm
      fd to omap_device, and the omap_device itself is reference counted.
      Per omap_device, we keep a handle_table mapping GEM handle to omap_bo.
      When buffers are imported from flink name or dmabuf fd, the handle
      table is consulted, and if an omap_bo already exists, it's refcnt is
      incremented and it is returned.  For good measure, to avoid the
      handle_table being deleted before the omap_bo is freed, the omap_bo
      holds a reference to the omap_device.
      
      TODO: check the overhead of the hashtable.  If too much we could maybe
      get away with only tracking exported and imported bo's in the table.
      
      TODO: all the import/export flink/dmabuf operations are generic DRM
      ioctls.  Really all this functionality could be handled by a generic
      drm_bo and drm_device "base class" that could be extended by omap,
      exynos, etc.  That would also allow more common userspace code by
      avoiding artificial libdrm_omap dependencies.
      
      Signed-off-by: default avatarRob Clark <rob@ti.com>
      22574aa8
    • Rob Clark's avatar
      omap: add API to import bo's from dmabuf fd's · 42f8a68e
      Rob Clark authored
      
      Signed-off-by: default avatarRob Clark <rob@ti.com>
      42f8a68e
    • Rob Clark's avatar
      omap: clarify dmabuf file descriptor ownership · 8116a32d
      Rob Clark authored
      
      Signed-off-by: default avatarRob Clark <rob@ti.com>
      8116a32d
  12. Jul 12, 2012
    • Kenneth Graunke's avatar
      intel: Change context create failure message to from fprintf to DBG(). · 992e2afd
      Kenneth Graunke authored
      
      Since there is no getparam for hardware context support, Mesa always
      tries to obtain a context by calling drm_intel_gem_context_create and
      NULL-checking the result.  On an older kernel without context support,
      this caused libdrm to print an unwanted message to stderr:
      
      DRM_IOCTL_I915_GEM_CONTEXT_CREATE failed: Invalid argument
      
      In fact, this caused every Piglit test to fail with a "warn" status due
      to the unrecognized error message.
      
      Change the message to use DBG() rather than fprintf(), so people can
      still get the debug message, but it won't spam normally.
      
      Reviewed-by: Ben Widawsky's avatarBen Widawsky <ben@bwidawsk.net>
      Signed-off-by: Kenneth Graunke's avatarKenneth Graunke <kenneth@whitecape.org>
      992e2afd
  13. Jul 06, 2012
  14. Jul 03, 2012
  15. Jun 29, 2012
  16. Jun 28, 2012
  17. Jun 27, 2012
Loading