Skip to content
  1. Mar 25, 2020
    • Chris Wilson's avatar
      drm/i915/execlists: Drop setting sibling priority hint on virtual engines · 9bf7c313
      Chris Wilson authored
      We set the priority hint on execlists to avoid executing the tasklet for
      when we know that there will be no change in execution order. However,
      as we set it from the virtual engine for all siblings, but only one
      physical engine may respond, we leave the hint set on the others
      stopping direct submission that could take place.
      
      If we do not set the hint, we may attempt direct submission even if we
      don't expect to submit. If we set the hint, we may not do any submission
      until the tasklet is run (and sometimes we may park the engine before
      that has had a chance). Ergo there's only a minor ill-effect on mixed
      virtual/physical engine workloads where we may try and fail to do direct
      submission more often than required. (Pure virtual / engine workloads
      will have redundant tasklet execution suppressed as normal.)
      
      Closes: https://gitlab.freedesktop.org/drm/intel/issues/1522
      
      
      Signed-off-by: default avatarChris Wilson <chris@chris-wilson.co.uk>
      Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
      Reviewed-by: default avatarTvrtko Ursulin <tvrtko.ursulin@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20200325101358.12231-1-chris@chris-wilson.co.uk
      9bf7c313
    • José Roberto de Souza's avatar
      drm/i915/display/fbc: Make fences a nice-to-have for GEN9+ · 691f7ba5
      José Roberto de Souza authored
      
      
      dGFX has local memory so it does not have aperture or support
      CPU fences but even for iGFX it have a small number of fences.
      
      As replacement for fences to track frontbuffer modifications by CPU
      we have a software tracking that is already in used by FBC and PSR.
      PSR don't support fences so it shows that this tracking is reliable.
      
      So lets make fences a nice-to-have to activate FBC for GEN9+, this
      will allow us to enable FBC for dGFXs and iGFXs even when there is no
      available fence.
      
      We do not set fences to rotated planes but FBC only have restrictions
      against 16bpp, so adding it here.
      
      Also adding a new check for the tiling format, fences are only set
      to X and Y tiled planes but again FBC don't have any restrictions
      against tiling so adding linear as supported as well, other formats
      should be added after tested but IGT only supports drawing in thse
      3 formats.
      
      intel_fbc_hw_tracking_covers_screen() maybe can also have the same
      treatment as fences but BSpec is not clear if the size limitation is
      for hardware tracking or general use of FBC and I don't have a 5K
      display to test it, so keeping as is for safety.
      
      v2:
      - Added tiling and pixel format rotation checks
      - Changed the GEN version not requiring fences to 11 from 9, DDX
      needs some changes but it don't have support for GEN11+
      
      v3:
      - Changed back to GEN9+
      - Moved GEN test to inside of tiling_is_valid()
      
      v4:
      - moved rotation check to its own functions
      
      v5:
      - renamed rotations_is_valid to rotation_is_valid
      - moved pre-g4x rotation check to rotation_is_valid()
      
      Cc: Daniel Vetter <daniel.vetter@intel.com>
      Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Reviewed-by: default avatarVille Syrjälä <ville.syrjala@linux.intel.com>
      Signed-off-by: default avatarJosé Roberto de Souza <jose.souza@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20200319211535.114625-1-jose.souza@intel.com
      691f7ba5
  2. Mar 24, 2020
  3. Mar 23, 2020
  4. Mar 22, 2020
  5. Mar 20, 2020
  6. Mar 19, 2020