13:05 johnny0: agd5f: does fiji actually take longer than other cards with smu7 to measure power?
13:06 johnny0: or was the change in f5742ec36422 to sleep for 500ms vs 1ms a subjective one?
13:09 johnny0: because a 500ms delay feels... bad, even when just typing 'sensors' -- it also causes GALLIUM_HUD to block for 500ms if both it and another program are checking power
13:15 johnny0: on Hawaii, output after 1ms seems fine, and enables per-frame updates of power / temperature / etc.
13:43 agd5f: johnny0, the firmware doesn't average it the driver does.
14:20 johnny0: thanks, that means userland can optionally smooth out the measurements by just increasing the sampling rate (with extra overhead, of course)
14:25 johnny0: Venemo: the above is a pain point moving from radeon to amdgpu -- i trip over it every once and a while and wonder what's happening until I realize I left something like `watch -n1 sensors amdgpu-*` open
14:26 Venemo: johnny0: wdym? fiji has always used amdgpu
14:30 johnny0: bonaire and hawaii users are impacted by the change as soon as they run 'sensors' for the first time
14:32 johnny0: with GALLIUM_HUD, I guess it reads a bunch of sensors at once (like with reading amdgpu_pm_info), so things like displaying temperature will stall the program if another monitoring utility is running
14:33 johnny0: mangohud looks to handle the situation more gracefully (guessing it's multithreaded), but there's still the artificial limitation of sensor refresh rate
14:40 Venemo: huh. so mangohud sucks on hawaii due to this?
14:46 johnny0: it's not rendered effectively unusable like GALLIUM_HUD is, but if you're used to sensors updates > 2Hz you're in for disappointment
14:48 johnny0: but it's not just the CIK cards, anything that uses smu7 is hamstrung like this
14:57 Venemo: johnny0: mangohud makes BG3 unplayable on Hawaii, with periodic hitches
14:57 Venemo: maybe it's due to this
15:02 johnny0: interesting, I couldn't get glxgears or vkcube to hitch with mangohud (besides the initial 500ms startup lag)