1. 10 10月, 2011 3 次提交
  2. 06 9月, 2011 2 次提交
  3. 02 9月, 2011 1 次提交
  4. 01 9月, 2011 2 次提交
    • M
      drm/radeon/kms: add a new gem_wait ioctl with read/write flags · d3ed7402
      Marek Olšák 提交于
      The new DRM_RADEON_GEM_WAIT ioctl combines GEM_WAIT_IDLE and GEM_BUSY (there
      is a NO_WAIT flag to get the latter) with USAGE_READ and USAGE_WRITE flags
      to take advantage of the new ttm_bo_wait changes.
      
      Also bump the DRM version.
      Signed-off-by: NMarek Olšák <maraeo@gmail.com>
      Reviewed-by: NJerome Glisse <jglisse@redhat.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      d3ed7402
    • M
      drm/ttm: add a way to bo_wait for either the last read or last write · dfadbbdb
      Marek Olšák 提交于
      Sometimes we want to know whether a buffer is busy and wait for it (bo_wait).
      However, sometimes it would be more useful to be able to query whether
      a buffer is busy and being either read or written, and wait until it's stopped
      being either read or written. The point of this is to be able to avoid
      unnecessary waiting, e.g. if a GPU has written something to a buffer and is now
      reading that buffer, and a CPU wants to map that buffer for read, it needs to
      only wait for the last write. If there were no write, there wouldn't be any
      waiting needed.
      
      This, or course, requires user space drivers to send read/write flags
      with each relocation (like we have read/write domains in radeon, so we can
      actually use those for something useful now).
      
      Now how this patch works:
      
      The read/write flags should passed to ttm_validate_buffer. TTM maintains
      separate sync objects of the last read and write for each buffer, in addition
      to the sync object of the last use of a buffer. ttm_bo_wait then operates
      with one the sync objects.
      Signed-off-by: NMarek Olšák <maraeo@gmail.com>
      Reviewed-by: NJerome Glisse <jglisse@redhat.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      dfadbbdb
  5. 31 8月, 2011 1 次提交
  6. 30 8月, 2011 2 次提交
  7. 23 8月, 2011 1 次提交
  8. 22 8月, 2011 4 次提交
  9. 15 8月, 2011 1 次提交
  10. 12 8月, 2011 5 次提交
  11. 04 8月, 2011 8 次提交
  12. 27 7月, 2011 1 次提交
  13. 26 7月, 2011 3 次提交
  14. 25 7月, 2011 6 次提交