1. 06 Mar, 2015 5 commits
  2. 05 Mar, 2015 1 commit
  3. 04 Mar, 2015 3 commits
    • Tim Gore's avatar
      tests/gem_render_tiled_blits: split into subtests · ee5c119c
      Tim Gore authored
      The gem_render_tiled_blits test tends to get oom killed
      on low memory (< 4GB) Android systems. This is because the
      test tries to allocate (sysinfo.totalram * 9 / 10) in
      buffer objects and the remaining 10% of memory is not
      always enough for the Android system.
      A similar issue with gem_render_linear_blits was resolved
      by creating several subtests. A "basic" subtest that uses
      minimal memory buffers to test the basic operation, and
      two stress tests which are skipped if there is insufficient
      memory. The first stress test uses more memory than the
      graphics apperture and the second uses enough to ensure
      that swap space is used (if present).
      This patch makes the same changes to gem_render_tiled_blits.
      
      v2: Following comments from Daniel Vetter:
        a) Use igt_main macro instead of "open coding", and
        b) cull some leading spaces
      Signed-off-by: default avatarTim Gore <tim.gore@intel.com>
      ee5c119c
    • Tim Gore's avatar
      tests/gem_render_linear_blits: split into two subtests · 9f90aabc
      Tim Gore authored
      The gem_render_linear_blits test tends to get oom killed
      on low memory (< 4GB) Android systems. This is because the
      test tries to allocate (sysinfo.totalram * 9 / 10) in
      buffer objects and the remaining 10% of memory is not
      always enough for the Android system.
      After a discussion with Chris Wilson I have split this
      test into a "basic" and an "apperture-thrash" subtest,
      in the same way as gem_linear_blits. The basic test
      uses just two buffer objects and the apperture-thrash
      test is skipped if there is insuffiecient memory.
      
      v2: Following comment from Chris Wilson:
          a) Remove the command line option for count.
          b) Add a third subtest to ensure swap is tested
      
      v3: Replace some leading spaces with tabs
      
      v4: Follwing comment from Daniel Vetter:
          a) Use igt_main macro instead of "open coding", and
          b) cull some more leading spaces
      Signed-off-by: default avatarTim Gore <tim.gore@intel.com>
      9f90aabc
    • Mika Kuoppala's avatar
      tools/intel_gtt: Add support for gen8 · 043f5869
      Mika Kuoppala authored
      Add 64bit ptes and 8MB mmiobar offset for gen8
      
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Cc: Ben Widawsky <benjamin.widawsky@intel.com>
      Acked-by: default avatarBen Widawsky <benjamin.widawsky@intel.com>
      Signed-off-by: default avatarMika Kuoppala <mika.kuoppala@intel.com>
      043f5869
  4. 02 Mar, 2015 1 commit
  5. 27 Feb, 2015 6 commits
  6. 26 Feb, 2015 3 commits
  7. 25 Feb, 2015 8 commits
  8. 24 Feb, 2015 2 commits
    • Marc Herbert's avatar
      lib/igt_kms.c: remove tests dependency on VT /dev/tty0 · c6d18ee5
      Marc Herbert authored
      Required to run on any recent, freon-based and X11-free ChromeOS release.
      
      v2:
      - igt_debug() instead of igt_warn()
      - return KD_GRAPHICS instead of -1UL
      - print previous mode in debug statements. Among others this help a tiny
        bit with the now confusing debug output ("cannot change" immediately
        followed by a misleading "mode changed").
      Signed-off-by: default avatarMarc Herbert <marc.herbert@intel.com>
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      c6d18ee5
    • David Weinehall's avatar
      tests/drv_suspend: hibernation test · 7890b093
      David Weinehall authored
      intel-gpu-tools currently has a bunch of tests for suspend,
      but currently none (that I could find) for hibernate.
      
      Attached is a rudimentary patch to add said test.  It does so
      by repurposing the drv_suspend driver to handle both suspend
      and hibernate, since the difference is miniscule.
      
      I decided to split the suspend/autoresume functions in
      igt_aux.c though, to be able to leave the igt_system_uspend_autoresume()
      function unchanged (the other option would be to
      introduce a boolean function argument and have that
      decide what parameters to pass to rtcwake).
      
      The timeout passed to rtcwake probably needs tuning (it might
      even need to be dynamically adjusted, since the time hibernation takes
      varies wildly depending on the amount of non-cache memory in use).
      Signed-off-by: default avatarDavid Weinehall <david.weinehall@intel.com>
      Reviewed-by: Imre Deak's avatarImre Deak <imre.deak@intel.com>
      7890b093
  9. 18 Feb, 2015 2 commits
  10. 17 Feb, 2015 4 commits
  11. 16 Feb, 2015 1 commit
  12. 13 Feb, 2015 4 commits