1. 26 Jan, 2016 3 commits
  2. 25 Jan, 2016 6 commits
    • Eric Anholt's avatar
      igt: Disable igt_clflush_range() implementation on ARM builds · ea3331d1
      Eric Anholt authored
      Daniel has suggested that I put vc4 testing into igt, since it's got
      the piglit integration and KMS coverage already.  This gets the ccore
      building so that I can start writing tests.
      Signed-off-by: Eric Anholt's avatarEric Anholt <eric@anholt.net>
      Reviewed-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
    • Daniel Stone's avatar
      build: Disable x86-specific utilities on non-x86 · bccc0ec6
      Daniel Stone authored
      Some bits can't be built on non-x86 architectures, mostly because they
      require x86-specific assembly primitives. Disable these by default on
      non-x86 architectures.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      Reviewed-by: Eric Anholt's avatarEric Anholt <eric@anholt.net>
    • Michał Winiarski's avatar
      lib/ioctl_wrappers: Add gem_has_softpin · e6ca4bd7
      Michał Winiarski authored
      We can move it from softpin test into lib, and since softpin support is
      highly unlikely to go away in-between getparam ioctl calls, let's just
      do a single call and store the value.
      v2: rebase
      Signed-off-by: Michał Winiarski's avatarMichał Winiarski <michal.winiarski@intel.com>
      Reviewed-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
    • Michał Winiarski's avatar
      lib/ioctl_wrappers: Add gem_gtt_type exposing raw HAS_ALIASING_PPGTT param · 52b5d501
      Michał Winiarski authored
      No functional changes.
      While I'm here, let's also rename gem_uses_aliasing_ppgtt (since it's
      being used to indicate if we are using ANY kind of ppgtt) and introduce
      gem_uses_full_ppgtt to drop some unnecessary code from tests that were
      previously calling getparam directly instead of using ioctl wrapper.
      v2: drop gem_uses_full_48b_ppgtt since it's no longer used anywhere,
          s/48b/64b (Chris)
      v3: rebase
      Cc: Chris Wilson <chris@chris-wilson.co.uk>
      Signed-off-by: Michał Winiarski's avatarMichał Winiarski <michal.winiarski@intel.com>
      Reviewed-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
    • Chris Wilson's avatar
    • Paulo Zanoni's avatar
      tools: add intel_residency · beb936f1
      Paulo Zanoni authored
      After the recent discussions regarding the effects of the vblank
      disabling policies on PC state residencies, I started running some
      experiments to reevaluate some non-intuitive conclusions I had
      reached. In order to help me do this, I decided to write this tool.
      The idea is very simple: the tool puts the system on an screen-on idle
      state, checks which PC state residency is the deepest we can reach,
      measures its residency, then does some not-so-idle tests and measures
      the residencies. You can use the tool to compare different Kernel
      trees and you can also use the tool to compare enabled vs disabled
      It's obvious that these cases do not represent real-world use cases of
      our driver, but they are already enough to highlight differences
      between the many patches I wrote. I was even able to catch a bug in
      one of my patches by spotting an unexpected regression in the
      I've been using this tool for FBC, but I expect it to also be useful
      for PSR, DRRS and similar features. I've been measuring the effects of
      different optimizations I wrote, and I've also been measuring the FBC
      vs no-FBC cases.
      It is also important to highlight that if your system is not properly
      configured for efficient power savings the tool may not be able to
      show differences between the results. On my Broadwell machine, for
      example, if I don't run "powertop --auto-tune" before running the
      tool, I get PC2 as the deepest state, and 90%+ residency for every
      workload. After properly configuring the machine, I get PC7 as the
      deepest state, which is the expected.
      So far I only tested this tool on BDW and SKL, and it may hit some
      unexpected assertions for older platforms.
      I only implemented the cases that are immediately useful for me, but
      we may also expand the tool in the future. We can add more important
      workloads. We can add support for screen-off cases, so we can compare
      the effects of runtime PM and other screen-off features. There's a lot
      we can do, but none of this is on my current priority list.
      And remember: /usr/bin/paste is your friend when comparing results.
        - Be more idle at setup_idle().
        - Improve printing for /usr/bin/paste usage.
      Signed-off-by: Paulo Zanoni's avatarPaulo Zanoni <paulo.r.zanoni@intel.com>
  3. 24 Jan, 2016 1 commit
  4. 23 Jan, 2016 3 commits
  5. 22 Jan, 2016 12 commits
  6. 21 Jan, 2016 2 commits
  7. 20 Jan, 2016 6 commits
  8. 19 Jan, 2016 7 commits