1. 16 6月, 2015 1 次提交
  2. 12 6月, 2015 2 次提交
  3. 28 5月, 2015 2 次提交
  4. 27 5月, 2015 1 次提交
    • C
      drm/i915: Use spinlocks for checking when to waitboost · 8d3afd7d
      Chris Wilson 提交于
      In commit 1854d5ca
      Author: Chris Wilson <chris@chris-wilson.co.uk>
      Date:   Tue Apr 7 16:20:32 2015 +0100
      
          drm/i915: Deminish contribution of wait-boosting from clients
      
      we removed an atomic timer based check for allowing waitboosting and
      moved it below the mutex taken during RPS. However, that mutex can be
      held for long periods of time on Vallyview/Cherryview as communication
      with the PCU is slow. As clients may frequently wait for results (e.g.
      such as tranform feedback) we introduced contention between the client
      and the RPS worker. We can take advantage of the RPS worker, by
      switching the wait boost decision to use spin locks and defer the
      actual reclocking to the worker.
      
      Fixes a regression of up to 45% on Baytrail and Baswell!
      
      v2 (Daniel):
      - Use max_freq_softlimit instead of the not-yet-merged boost
        frequency.
      - Don't inject a fake irq into the boost work, instead treat
        client_boost as just another legit waker.
      
      v3: Drop the now unused mask (Chris).
      
      Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90112
      Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> (v1)
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      8d3afd7d
  5. 22 5月, 2015 5 次提交
  6. 21 5月, 2015 4 次提交
  7. 20 5月, 2015 5 次提交
  8. 19 5月, 2015 1 次提交
  9. 08 5月, 2015 3 次提交
  10. 16 4月, 2015 1 次提交
  11. 14 4月, 2015 4 次提交
  12. 13 4月, 2015 1 次提交
  13. 10 4月, 2015 7 次提交
  14. 09 4月, 2015 1 次提交
  15. 31 3月, 2015 1 次提交
  16. 26 3月, 2015 1 次提交