1. 07 May, 2019 4 commits
  2. 29 Apr, 2019 1 commit
  3. 10 Apr, 2019 1 commit
  4. 08 Mar, 2019 10 commits
  5. 07 Mar, 2019 12 commits
  6. 25 Feb, 2019 3 commits
  7. 21 Feb, 2019 2 commits
  8. 14 Feb, 2019 1 commit
  9. 11 Feb, 2019 1 commit
    • Francisco Jerez's avatar
      intel/dump_gpu: Disambiguate between BOs from different GEM handle spaces. · 374eb3cd
      Francisco Jerez authored
      This fixes a rather astonishing problem that came up while debugging
      an issue in the Vulkan CTS.  Apparently the Vulkan CTS framework has
      the tendency to create multiple VkDevices, each one with a separate
      DRM device FD and therefore a disjoint GEM buffer object handle space.
      Because the intel_dump_gpu tool wasn't making any distinction between
      buffers from the different handle spaces, it was confusing the
      instruction state pools from both devices, which happened to have the
      exact same GEM handle and PPGTT virtual address, but completely
      different shader contents.  This was causing the simulator to believe
      that the vertex pipeline was executing a fragment shader, which didn't
      end up well.
      Reviewed-by: default avatarLionel Landwerlin <lionel.g.landwerlin@intel.com>
      374eb3cd
  10. 31 Jan, 2019 3 commits
  11. 14 Jan, 2019 1 commit
  12. 28 Dec, 2018 1 commit