1. 14 8月, 2015 1 次提交
    • T
      drm/vmwgfx: Fix execbuf locking issues · 3e04e2fe
      Thomas Hellstrom 提交于
      This addresses two issues that cause problems with viewperf maya-03 in
      situation with memory pressure.
      
      The first issue causes attempts to unreserve buffers if batched
      reservation fails due to, for example, a signal pending. While previously
      the ttm_eu api was resistant against this type of error, it is no longer
      and the lockdep code will complain about attempting to unreserve buffers
      that are not reserved. The issue is resolved by avoid calling
      ttm_eu_backoff_reservation in the buffer reserve error path.
      
      The second issue is that the binding_mutex may be held when user-space
      fence objects are created and hence during memory reclaims. This may cause
      recursive attempts to grab the binding mutex. The issue is resolved by not
      holding the binding mutex across fence creation and submission.
      Signed-off-by: NThomas Hellstrom <thellstrom@vmware.com>
      Reviewed-by: NSinclair Yeh <syeh@vmware.com>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      3e04e2fe
  2. 12 3月, 2015 2 次提交
    • C
      drm/vmwgfx: Correctly NULLify dma buffer pointer on failure · da5efffc
      Colin Ian King 提交于
      cppcheck on lines 917 and 977 show an ineffective assignment
      to the dma buffer pointer:
      
      [drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c:917]:
      [drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c:977]:
        (warning) Assignment of function parameter has no effect
        outside the function. Did you forget dereferencing it?
      
      On a successful DMA buffer lookup, the dma buffer pointer is
      assigned, however, on failure it currently is left in an
      undefined state.
      
      The original intention in the error exit path was to nullify
      the pointer on an error (which the original code failed to
      do properly). This patch fixes this also ensures all failure
      paths nullify the buffer pointer on the error return.
      
      Fortunately the callers to vmw_translate_mob_ptr and
      vmw_translate_guest_ptr are checking on a return status and not
      on the dma buffer pointer, so the original code worked.
      Reviewed-by: NThomas Hellstrom <thellstrom@vmware.com>
      Signed-off-by: NColin Ian King <colin.king@canonical.com>
      da5efffc
    • T
      drm/vmwgfx: Fix a couple of lock dependency violations · 5151adb3
      Thomas Hellstrom 提交于
      Experimental lockdep annotation added to the TTM lock has unveiled a
      couple of lock dependency violations in the vmwgfx driver. In both
      cases it turns out that the device_private::reservation_sem is not
      needed so the offending code is moved out of that lock.
      
      Cc: <stable@vger.kernel.org>
      Acked-by: NSinclair Yeh <syeh@vmware.com>
      Signed-off-by: NThomas Hellstrom <thellstrom@vmware.com>
      5151adb3
  3. 04 12月, 2014 1 次提交
  4. 11 9月, 2014 1 次提交
  5. 02 9月, 2014 2 次提交
  6. 01 9月, 2014 3 次提交
  7. 04 7月, 2014 1 次提交
  8. 24 4月, 2014 1 次提交
  9. 28 3月, 2014 1 次提交
  10. 13 2月, 2014 1 次提交
  11. 12 2月, 2014 3 次提交
  12. 05 2月, 2014 5 次提交
  13. 17 1月, 2014 12 次提交
  14. 28 6月, 2013 1 次提交
  15. 10 12月, 2012 1 次提交
    • M
      drm/ttm: remove no_wait_reserve, v3 · 97a875cb
      Maarten Lankhorst 提交于
      All items on the lru list are always reservable, so this is a stupid
      thing to keep. Not only that, it is used in a way which would
      guarantee deadlocks if it were ever to be set to block on reserve.
      
      This is a lot of churn, but mostly because of the removal of the
      argument which can be nested arbitrarily deeply in many places.
      
      No change of code in this patch except removal of the no_wait_reserve
      argument, the previous patch removed the use of no_wait_reserve.
      
      v2:
       - Warn if -EBUSY is returned on reservation, all objects on the list
         should be reservable. Adjusted patch slightly due to conflicts.
      v3:
       - Focus on no_wait_reserve removal only.
      Signed-off-by: NMaarten Lankhorst <maarten.lankhorst@canonical.com>
      Reviewed-by: NThomas Hellstrom <thellstrom@vmware.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      97a875cb
  16. 21 11月, 2012 1 次提交
  17. 20 11月, 2012 1 次提交
  18. 03 10月, 2012 1 次提交
  19. 13 2月, 2012 1 次提交