1. 23 Oct, 2018 1 commit
  2. 06 Jul, 2018 1 commit
  3. 20 Mar, 2018 1 commit
  4. 23 Feb, 2018 1 commit
    • Chris Wilson's avatar
      Iterate over physical engines · 305ebced
      Chris Wilson authored
      We current have a single for_each_engine() iterator which we use to
      generate both a set of uABI engines and a set of physical engines.
      Determining what uABI ring-id corresponds to an actual HW engine is
      tricky, so pull that out to a library function and introduce
      for_each_physical_engine() for cases where we want to issue requests
      once on each HW ring (avoiding aliasing issues).
      
      v2: Remember can_store_dword for gem_sync
      v3: Find more open-coded for_each_physical
      Signed-off-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
      Reviewed-by: Tvrtko Ursulin's avatarTvrtko Ursulin <tvrtko.ursulin@intel.com>
      305ebced
  5. 07 Sep, 2017 1 commit
  6. 18 May, 2017 1 commit
  7. 10 May, 2017 2 commits
  8. 13 Apr, 2017 2 commits
  9. 22 Mar, 2017 1 commit
  10. 22 Feb, 2017 1 commit
  11. 17 Feb, 2017 1 commit
  12. 06 Feb, 2017 1 commit
  13. 04 Feb, 2017 1 commit
  14. 26 Jan, 2017 2 commits
  15. 02 Jan, 2017 1 commit
  16. 18 Nov, 2016 2 commits
  17. 09 Nov, 2016 1 commit
  18. 07 Nov, 2016 1 commit
  19. 01 Apr, 2016 1 commit
  20. 14 Mar, 2016 1 commit
  21. 19 Feb, 2016 1 commit
  22. 28 Jan, 2016 2 commits