1. 23 Oct, 2018 1 commit
  2. 20 Mar, 2018 1 commit
  3. 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
  4. 07 Feb, 2018 1 commit
  5. 18 May, 2017 1 commit
  6. 08 Apr, 2017 1 commit
  7. 22 Feb, 2017 1 commit
  8. 03 Feb, 2017 1 commit
  9. 02 Jan, 2017 1 commit
  10. 17 Jun, 2016 1 commit
  11. 02 Jun, 2016 1 commit
  12. 27 Apr, 2016 1 commit