1. 04 5月, 2023 1 次提交
  2. 15 4月, 2023 1 次提交
  3. 13 4月, 2023 1 次提交
  4. 31 3月, 2023 2 次提交
  5. 16 3月, 2023 2 次提交
  6. 14 3月, 2023 3 次提交
  7. 24 2月, 2023 1 次提交
  8. 04 1月, 2023 1 次提交
  9. 21 12月, 2022 1 次提交
  10. 14 12月, 2022 1 次提交
  11. 10 11月, 2022 1 次提交
    • F
      drm/amdgpu: Set MTYPE in PTE based on BO flags · d1a372af
      Felix Kuehling 提交于
      The same BO may need different MTYPEs and SNOOP flags in PTEs depending
      on its current location relative to the mapping GPU. Setting MTYPEs from
      clients ahead of time is not practical for coherent memory sharing.
      Instead determine the correct MTYPE for the desired coherence model and
      current BO location when updating the page tables.
      
      To maintain backwards compatibility with MTYPE-selection in
      AMDGPU_VA_OP_MAP, the coherence-model-based MTYPE selection is only
      applied if it chooses an MTYPE other than MTYPE_NC (the default).
      
      Add two AMDGPU_GEM_CREATE_... flags to indicate the coherence model. The
      default if no flag is specified is non-coherent (i.e. coarse-grained
      coherent at dispatch boundaries).
      
      Update amdgpu_amdkfd_gpuvm.c to use this new method to choose the
      correct MTYPE depending on the current memory location.
      
      v2:
      * check that bo is not NULL (e.g. PRT mappings)
      * Fix missing ~ bitmask in gmc_v11_0.c
      v3:
      * squash in "drm/amdgpu: Inherit coherence flags on dmabuf import"
      Suggested-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NFelix Kuehling <Felix.Kuehling@amd.com>
      Acked-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      d1a372af
  12. 22 9月, 2022 1 次提交
  13. 20 9月, 2022 1 次提交
  14. 17 8月, 2022 1 次提交
  15. 11 8月, 2022 1 次提交
  16. 09 4月, 2022 1 次提交
  17. 26 3月, 2022 2 次提交
  18. 05 3月, 2022 1 次提交
  19. 03 3月, 2022 3 次提交
  20. 18 2月, 2022 2 次提交
  21. 15 2月, 2022 4 次提交
  22. 10 2月, 2022 1 次提交
  23. 28 1月, 2022 1 次提交
  24. 26 1月, 2022 1 次提交
  25. 20 1月, 2022 2 次提交
  26. 19 1月, 2022 1 次提交
  27. 15 1月, 2022 2 次提交
    • Y
      drm/amdgpu: Modify umc block to fit for the unified ras block data and ops · efe17d5a
      yipechai 提交于
      1.Modify umc block to fit for the unified ras block data and ops.
      2.Change amdgpu_umc_ras_funcs to amdgpu_umc_ras, and the corresponding variable name remove _funcs suffix.
      3.Remove the const flag of umc ras variable so that umc ras block can be able to be inserted into amdgpu device ras block link list.
      4.Invoke amdgpu_ras_register_ras_block function to register umc ras block into amdgpu device ras block link list.
      5.Remove the redundant code about umc in amdgpu_ras.c after using the unified ras block.
      6.Fill unified ras block .name .block .ras_late_init and .ras_fini for all of umc versions. If .ras_late_init and .ras_fini had been defined by the selected umc version, the defined functions will take effect; if not defined, default fill them with amdgpu_umc_ras_late_init and amdgpu_umc_ras_fini.
      Signed-off-by: Nyipechai <YiPeng.Chai@amd.com>
      Reviewed-by: NHawking Zhang <Hawking.Zhang@amd.com>
      Reviewed-by: NJohn Clements <john.clements@amd.com>
      Reviewed-by: NTao Zhou <tao.zhou1@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      efe17d5a
    • Y
      drm/amdgpu: Modify mmhub block to fit for the unified ras block data and ops · 5e67bba3
      yipechai 提交于
      1.Modify mmhub block to fit for the unified ras block data and ops.
      2.Change amdgpu_mmhub_ras_funcs to amdgpu_mmhub_ras, and the corresponding variable name remove _funcs suffix.
      3.Remove the const flag of mmhub ras variable so that mmhub ras block can be able to be inserted into amdgpu device ras block link list.
      4.Invoke amdgpu_ras_register_ras_block function to register mmhub ras block into amdgpu device ras block link list. 5.Remove the redundant code about mmhub in amdgpu_ras.c after using the unified ras block.
      5.Remove the redundant code about mmhub in amdgpu_ras.c after using the unified ras block.
      6.Fill unified ras block .name .block .ras_late_init and .ras_fini for all of mmhub versions. If .ras_late_init and .ras_fini had been defined by the selected mmhub version, the defined functions will take effect; if not defined, default fill them with amdgpu_mmhub_ras_late_init and amdgpu_mmhub_ras_fini.
      Signed-off-by: Nyipechai <YiPeng.Chai@amd.com>
      Reviewed-by: NHawking Zhang <Hawking.Zhang@amd.com>
      Reviewed-by: NJohn Clements <john.clements@amd.com>
      Reviewed-by: NTao Zhou <tao.zhou1@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      5e67bba3