1. 23 Jun, 2021 2 commits
    • Jiawei Gu's avatar
      tests/amdgpu: Add vbios info query test · 6488232d
      Jiawei Gu authored
      
      Signed-off-by: Jiawei Gu's avatarJiawei Gu <Jiawei.Gu@amd.com>
      6488232d
    • Jiawei Gu's avatar
      amdgpu: sync up amdgpu_drm.h with latest from kernel · bc327728
      Jiawei Gu authored
      
      
      From drm-next:
      
      commit 17f99c747e7c3861a0eed12ab3f7a9233292eac9
      Author: Jiawei Gu <Jiawei.Gu@amd.com>
      Date:   Thu May 20 10:37:28 2021 +0800
      
          drm/amdgpu: Add vbios info ioctl interface
      
          Add AMDGPU_INFO_VBIOS_INFO subquery id for detailed vbios info.
      
          Provides a way for the user application to get the VBIOS
          information without having to parse the binary.
          It is useful for the user to be able to display in a simple way the VBIOS
          version in their system if they happen to encounter an issue.
      
          V2:
          Use numeric serial.
          Parse and expose vbios version string.
      
          V3:
          Remove redundant data in drm_amdgpu_info_vbios struct.
      
          V4:
          64 bit alignment in drm_amdgpu_info_vbios.
      Signed-off-by: Jiawei Gu's avatarJiawei Gu <Jiawei.Gu@amd.com>
      bc327728
  2. 22 Jun, 2021 6 commits
  3. 20 Jun, 2021 3 commits
  4. 15 Jun, 2021 1 commit
    • Bas Nieuwenhuizen's avatar
      amdgpu: Add vamgr for capture/replay. · 085ee3e4
      Bas Nieuwenhuizen authored
      
      
      In Vulkan we have extensions to assist with capture in replay in a
      world where addresses are returned to the application. This involves
      creating buffers at the same VA during replay as they were during
      capture.
      
      By itself libdrm_amdgpu already has support for this, but there is
      the obvious failure mode that if another buffer is already allocated
      at that VA things fail spectacularly. This is an actual issue as
      internal buffers, like winsys images or shader binaries also
      participate in the same VA allocation.
      
      To avoid this problem applications have to create buffers which
      are going to be captured with a flag, and the implementation is to
      separate VA allocation for those buffers to reduce the collision risk:
      
      "Implementations are expected to separate such buffers in the GPU address
      space so normal allocations will avoid using these addresses. Apps/tools
      should avoid mixing app-provided and implementation-provided addresses for
      buffers created with VK_BUFFER_CREATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT,
      to avoid address space allocation conflicts."
      
      This patch implements that by adding a flag for these buffers and allocating
      address space from the top of the address range instead of the bottom.
      Signed-off-by: Bas Nieuwenhuizen's avatarBas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
      Reviewed-by: Christian König's avatarChristian König <christian.koenig@amd.com>
      085ee3e4
  5. 09 Jun, 2021 6 commits
  6. 07 Jun, 2021 1 commit
  7. 01 Jun, 2021 1 commit
  8. 20 May, 2021 1 commit
  9. 18 May, 2021 1 commit
  10. 06 May, 2021 6 commits
  11. 30 Apr, 2021 2 commits
  12. 22 Apr, 2021 1 commit
  13. 19 Apr, 2021 1 commit
  14. 14 Apr, 2021 2 commits
  15. 12 Apr, 2021 1 commit
  16. 09 Apr, 2021 1 commit
  17. 07 Apr, 2021 1 commit
  18. 06 Apr, 2021 3 commits