OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

amd/rgp: Use VGH clocks for RGP workaround.

Browse Source 
Hear that it matters for RGP. This is the most likely scenario where
we would hit this workaround, given the tooling for profiling on the
deck will set profile_peak as workaround for hangs.

Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13534>
This commit is contained in:
Bas Nieuwenhuizen
2021-10-27 01:49:23 +02:00
committed by Marge Bot
parent bfbc41a9fa
commit 2c43fd4c41
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/amd/common/ac_rgp.c
View File

@@ -453,12 +453,12 @@ static void ac_sqtt_fill_asic_info(struct radeon_info *rad_info,
chunk->trace_shader_core_clock = rad_info->max_shader_clock * 1000000;
chunk->trace_memory_clock = rad_info->max_memory_clock * 1000000;
/* RGP gets very confused if these clocks are 0. The 1 GHz clocks are not necessarily correct,
* but the resulting traces are at least somewhat useful. */
/* RGP gets very confused if these clocks are 0. The numbers here are for profile_peak on
* VGH since that is the chips where we've seen the need for this workaround. */
if (!chunk->trace_shader_core_clock)
chunk->trace_shader_core_clock = 1e9;
chunk->trace_shader_core_clock = 1300000000;
if (!chunk->trace_memory_clock)
chunk->trace_memory_clock = 1e9;
chunk->trace_memory_clock = 687000000;
chunk->device_id = rad_info->pci_id;
chunk->device_revision_id = rad_info->pci_rev_id;