Comment # 1 on bug 102683 from Niklas Haas

Re-testing this I noticed that it's possible */amdgpu_pm_info just delivers
more unrealiable data or something; with GALLIUM_HUD_PERIOD=0
GALLIUM_HUD=shader-clock,gpu-load I noticed it working much better.

As for the “performance issues”, I think it may be because of timers getting
confused due to the change in frequency? Re-testing I can't notice more dropped
frames than usual except at the very beginning, probably due to the very fact
that it does frequency scaling.

I'll close this issue unless I have something more concrete to report.