|Summary:||[r600g] GPU load always displayed at 100% with GALLIUM_HUD=GPU-load|
|Component:||Drivers/Gallium/r600||Assignee:||Default DRI bug account <dri-devel>|
|Status:||RESOLVED MOVED||QA Contact:||Default DRI bug account <dri-devel>|
|i915 platform:||i915 features:|
Description MWATTT 2017-02-25 00:38:05 UTC
Hello, The GPU-load graph from GALLIUM_HUD will always be at 100%, no matter what application is launched (even glxgears with vblank_mode=3). I tested that on my Radeon HD 5770. This regression is caused by commit b8f3b00742eab6ee1868407b876f69195a51f3b6 : gallium/radeon: include SDMA in the GPU load query. It doesn't seems to affect radeonsi, as the GPU-load results on a TOPAZ XT chip are more reasonable (~5% with the same test).
Comment 1 Hleb Valoshka 2017-03-05 17:46:52 UTC
This bug affects radeonsi as well (HW - 7750, kernel - Linux 4.10.0-rc8, amdgpu kernel driver). When this commit (b8f3b007) is reverted, then hud shows a correct value.
Comment 2 Alex Deucher 2017-03-06 15:20:21 UTC
Comment 3 Alex Deucher 2017-03-06 15:53:00 UTC
Comment 4 Jan Ziak (http://atom-symbol.net) 2017-03-31 07:42:38 UTC
I am still experiencing this issue on a R9-390 GPU with Mesa git-469da09.
Comment 5 Alex Deucher 2017-03-31 14:36:42 UTC
(In reply to Jan Ziak from comment #4) > I am still experiencing this issue on a R9-390 GPU with Mesa git-469da09. What kernel are you using?
Comment 6 Jan Ziak (http://atom-symbol.net) 2017-03-31 15:01:54 UTC
(In reply to Alex Deucher from comment #5) > (In reply to Jan Ziak from comment #4) > > I am still experiencing this issue on a R9-390 GPU with Mesa git-469da09. > > What kernel are you using? - radeontop is working OK. $ uname -r 4.11.0-rc4+ $ glversion 4.5 (Core Profile) Mesa 17.1.0-devel (git-02112c3) Gallium 0.4 on AMD HAWAII (DRM 3.10.0 / 4.11.0-rc4+, LLVM 4.0.0) $ cat ~/bin/shared/glversion #!/bin/bash set -e unset LIBGL_DEBUG INFO="$(glxinfo)" echo "$INFO" | grep "OpenGL core profile version" | sed "s/^.*: *//" echo "$INFO" | grep "renderer string" | sed "s/^.*: *//"
Comment 7 GitLab Migration User 2019-09-18 19:22:52 UTC
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/598.
Comment 8 Jan Ziak (http://atom-symbol.net) 2019-09-19 13:46:37 UTC
Hi. Just a note about the migration process: Bugzilla migration to https://gitlab.freedesktop.org/mesa/mesa/issues/598 is failing to preserve newline characters found in this bug report. This seems to be the case only when the line starts with an $.