“5ad5a8199e3b3e1162af50c0a52eca678a259d67”上不存在“deploy/pptracking/python/mot_jde_infer.py”
  1. 14 9月, 2022 1 次提交
  2. 16 3月, 2022 1 次提交
  3. 12 2月, 2022 1 次提交
  4. 10 2月, 2022 1 次提交
  5. 28 1月, 2022 1 次提交
  6. 29 10月, 2021 2 次提交
  7. 20 10月, 2021 1 次提交
  8. 24 9月, 2021 1 次提交
    • M
      drm/amdgpu: Drop inline from amdgpu_ras_eeprom_max_record_count · 6cd1f9b4
      Michel Dänzer 提交于
      This was unusual; normally, inline functions are declared static as
      well, and defined in a header file if used by multiple compilation
      units. The latter would be more involved in this case, so just drop
      the inline declaration for now.
      
      Fixes compile failure building for ppc64le on RHEL 8:
      
      In file included from ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras.h:32,
                       from ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c:33:
      ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c: In function ‘amdgpu_ras_recovery_init’:
      ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.h:90:17: error: inlining failed in call
       to ‘always_inline’ ‘amdgpu_ras_eeprom_max_record_count’: function body not available
         90 | inline uint32_t amdgpu_ras_eeprom_max_record_count(void);
            |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c:1985:34: note: called from here
       1985 |         max_eeprom_records_len = amdgpu_ras_eeprom_max_record_count();
            |                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      Fixes: c84d4670 "drm/amdgpu: validate bad page threshold in ras(v3)"
      Reviewed-by: NLyude Paul <lyude@redhat.com>
      Signed-off-by: NMichel Dänzer <mdaenzer@redhat.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      6cd1f9b4
  9. 16 9月, 2021 1 次提交
    • M
      drm/amdgpu: Drop inline from amdgpu_ras_eeprom_max_record_count · 114518ff
      Michel Dänzer 提交于
      This was unusual; normally, inline functions are declared static as
      well, and defined in a header file if used by multiple compilation
      units. The latter would be more involved in this case, so just drop
      the inline declaration for now.
      
      Fixes compile failure building for ppc64le on RHEL 8:
      
      In file included from ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras.h:32,
                       from ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c:33:
      ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c: In function ‘amdgpu_ras_recovery_init’:
      ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.h:90:17: error: inlining failed in call
       to ‘always_inline’ ‘amdgpu_ras_eeprom_max_record_count’: function body not available
         90 | inline uint32_t amdgpu_ras_eeprom_max_record_count(void);
            |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      ../drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c:1985:34: note: called from here
       1985 |         max_eeprom_records_len = amdgpu_ras_eeprom_max_record_count();
            |                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      Fixes: c84d4670 "drm/amdgpu: validate bad page threshold in ras(v3)"
      Reviewed-by: NLyude Paul <lyude@redhat.com>
      Signed-off-by: NMichel Dänzer <mdaenzer@redhat.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      114518ff
  10. 31 8月, 2021 1 次提交
  11. 06 8月, 2021 2 次提交
  12. 09 7月, 2021 3 次提交
  13. 01 7月, 2021 18 次提交
  14. 10 4月, 2021 1 次提交
  15. 24 3月, 2021 2 次提交
    • S
      drm/amdgpu: fix send ras disable cmd when asic not support ras · 970fd197
      Stanley.Yang 提交于
          cause:
      	It is necessary to send ras disable command to ras-ta during gfx
      	block ras later init, because the ras capability is disable read
      	from vbios for vega20 gaming, but the ras context is released
      	during ras init process, this will cause send ras disable command
      	to ras-to failed.
          how:
      	Delay releasing ras context, the ras context
      	will be released after gfx block later init done.
      
      Changed from V1:
          move release_ras_context into ras_resume
      
      Changed from V2:
          check BIT(UMC) is more reasonable before access eeprom table
      Signed-off-by: NStanley.Yang <Stanley.Yang@amd.com>
      Reviewed-by: NHawking Zhang <Hawking.Zhang@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      970fd197
    • S
      drm/amdgpu: Reset the devices in the XGMI hive duirng probe · e3c1b071
      shaoyunl 提交于
      In passthrough configuration, hypervisior will trigger the SBR(Secondary bus reset) to the devices
      without sync to each other. This could cause device hang since for XGMI configuration, all the devices
      within the hive need to be reset at a limit time slot. This serial of patches try to solve this issue
      by co-operate with new SMU which will only do minimum house keeping to response the SBR request but don't
      do the real reset job and leave it to driver. Driver need to do the whole sw init and minimum HW init
      to bring up the SMU and trigger the reset(possibly BACO) on all the ASICs at the same time
      Signed-off-by: Nshaoyunl <shaoyun.liu@amd.com>
      Acked-by: Andrey Grodzovsky andrey.grodzovsky@amd.com
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      e3c1b071
  16. 27 2月, 2021 1 次提交
  17. 07 1月, 2021 1 次提交
  18. 06 1月, 2021 1 次提交