1. 11 Mar, 2019 16 commits
  2. 08 Mar, 2019 8 commits
  3. 07 Mar, 2019 1 commit
  4. 06 Mar, 2019 3 commits
  5. 05 Mar, 2019 2 commits
    • Dale B Stimson's avatar
      gem_ctx_isolation.c - Gen11 enabling for context isolation test · 67c72249
      Dale B Stimson authored
      This patch is a change to igt file tests/i915/gem_ctx_isolation.c to
      add and enable Gen11 support.
      
      This patch accounts for whitelisted registers appropriately for the
      different Gen levels.
      
      This patch accounts for the changed MMIO offsets of Gen11.
      
      This patch redefines MAX_REG from 0x40000 to 0x200000 due to the
      larger total register space for Gen11 mmio offsets.
      
      A current Gen11 SKU has two video engines (with indexes 0 and 2,
      for VCS0 and VCS2), with VCS1 not being used.
      
      Current kernel and igt limitations only allow for VCS0 and VCS1.
      Those limitations are in the process of being removed.  See for
      example the RFC/PATCH series on igt-dev from Andy Shyti:
          [igt-dev] [RFC PATCH v9 0/5] new engine discovery interface
      which depends on in-process kernel "media scalability" patches.
      
      Lacking the above infrastructure at the moment:
      
      The array of registers to be tested includes VCS2 and VCS3 registers.
      They are present as a provision for the future, but they will
      not actually be tested as those engines are not yet known to the
      underlying infrastructure.
      
      When run on Gen11 this patch skips the sub-tests for the non-existent VCS1
      with these warnings:
        Test requirement not met in function gem_require_engine, file ../lib/igt_gt.h:114:
        Test requirement: gem_has_engine(gem_fd, class, instance)
      Signed-off-by: 's avatarDale B Stimson <dale.b.stimson@intel.com>
      Reviewed-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      67c72249
    • Chris Wilson's avatar
      i915/gem_busy: Another year, another ABI bump · 8feb1475
      Chris Wilson authored
      The ABI ring ids are dead. Long live our classes.
      Signed-off-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
      Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
      Reviewed-by: Tvrtko Ursulin's avatarTvrtko Ursulin <tvrtko.ursulin@intel.com>
      8feb1475
  6. 04 Mar, 2019 3 commits
    • Nicholas Kazlauskas's avatar
      lib/igt_kms: Fix commits for planes with multiple possible CRTCs · ed944b45
      Nicholas Kazlauskas authored
      An igt_plane_t is defined per igt_pipe_t. It is treated as its
      own independent resource but DRM planes can be exposed to being used on
      a number of possible CRTCs - making it a shared resource.
      
      In IGT planes with multiple possible CRTCs are added to the plane list
      for each pipe that the plane supports. The internal state remains
      independent in IGT so when the same plane is modified for multiple
      pipes in a single commit the last pipe to modify it is the one whose
      state gets fully applied.
      
      This situation happens fairly often in practice - resetting the display
      at the start of the test before a commit will reset the CRTC ID and FB
      ID for each plane.
      
      For an example, consider the
      igt@kms_plane_alpha_blend@pipe-a-constant-alpha-max test.
      
      This test will fail for any overlay plane exposed for multiple CRTCs.
      
      The test tries to set a framebuffer for pipe A but has all the other
      pipes reset the plane state in the same commit. If there are multiple
      pipes on the hardware then the last pipe will be the one to set all the
      plane properties. The driver will receive a commit with no overlay
      plane enabled since the last pipe set CRTC ID and FB ID to 0, disabling
      the plane. The reference CRC capture will be incorrect since not all
      the planes have been enabled and the subsequent CRC captures will
      not match, failing the test.
      
      The simplest (but hacky) fix to this problem is to only set the
      properties for the plane for the pipe that last had it bound.
      
      This patch introduces a global plane list on igt_display_t that keeps
      track of the pipe that pipe that last called igt_plane_set_fb. The
      properties for the plane will only be applied from that single pipe
      when commiting the state to DRM.
      
      No behavioral changes should be introduced by this patch for hardware
      whose planes are only ever exposed one CRTC.
      
      It would likely be best to eventually modify the igt_pipe_t plane list
      to be a list of pointers to planes instead (igt_plane_t**)
      instead of being the actual plane objects, but that can come later.
      
      Many areas of the code like to make use of the backpointer to the pipe
      on the plane which makes refactoring the code in that manner a little
      trickier.
      
      v2: Add igt_plane_set_fb, use igt_plane_t for global plane list (Daniel)
      v3: Leave TODO for filling in all state/props on global planes
      
      Cc: Daniel Vetter <daniel@ffwll.ch>
      Signed-off-by: Nicholas Kazlauskas's avatarNicholas Kazlauskas <nicholas.kazlauskas@amd.com>
      Reviewed-by: Harry Wentland's avatarHarry Wentland <harry.wentland@amd.com>
      ed944b45
    • Tvrtko Ursulin's avatar
      automake: Make librt mandatory · a958d3f6
      Tvrtko Ursulin authored
      librt is required by libintel_tools so express it as mandatory in autoconf
      and also drop explicit mentions from Makefile.am.
      
      This also fixes a build warning of:
      
        tests/Makefile.am:134: warning: variable 'pm_rc6_residency_LDADD' is defined but no program or
        tests/Makefile.am:134: library has 'pm_rc6_residency' as canonical name (possible typo)
      Signed-off-by: Tvrtko Ursulin's avatarTvrtko Ursulin <tvrtko.ursulin@intel.com>
      Reviewed-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      a958d3f6
    • Tvrtko Ursulin's avatar
      autoconf: Silence void pointer arithmetic warnings · a117a5b8
      Tvrtko Ursulin authored
      Meson build does it so make the two symmetrical in this respect.
      
      v2:
       * Do it properly. (Chris Wilson)
      Signed-off-by: Tvrtko Ursulin's avatarTvrtko Ursulin <tvrtko.ursulin@intel.com>
      Reviewed-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      a117a5b8
  7. 02 Mar, 2019 2 commits
  8. 01 Mar, 2019 5 commits