Repository navigation
Conversation
Disk image
Downloads as a zip holding |
fedaab0 to
7d1347d
Compare
Overlay rendering
Files changed
Tested onRetroid Pocket 6 (SM8550/QCS8550, Adreno 740), Linux 6.5+ mainline
How to Install
|
|
Let’s discuss this. I’ve found a new issue. |
msm shares RAM with the CPU and exposes no system-wide VRAM counter, so the VRAM row always read 0.0. Use the client's drm-resident-memory (Linux 6.5+) for the VRAM row and PVRAM on msm_dpu, and show the share of MemTotal in use next to the used RAM value. Drop the smaller "/total" suffix that crowded the used value, and move swap to a labelled SWAP row. Hide the VRAM memory-temp, GPU temp and memory-clock cells when no sensor backs them; msm has no vram sensor or memory clock, and these handhelds have no RAM spd5118, so those cells rendered a constant 0°C / 0 MHz. Pick gpuss_0_thermal deterministically for the GPU temperature instead of whichever hwmon device containing "gpu" is enumerated first, and fall back to the gpuss-* thermal zones when no GPU hwmon exists.
7d1347d to
92354c5
Compare



Summary
On Armada's unified-memory handhelds the MangoHud/mangoapp overlay always
reports
VRAM 0.0 GiB. The msm driver has no system-wide VRAM counter, soMangoHud's
msm_dpupath leavesdrm_memory_typeunset and bothVRAMandPVRAMremain at zero. TheRAMrow also only shows used memory, with noindication of the device's total.
This adds an Armada MangoHud patch that:
drm-resident-memory, whichmsm has exposed through fdinfo since Linux 6.5, so
PVRAMreports realusage;
VRAMrow onmsm_dpu, where no system-wide VRAMcounter exists;
RAMrow asused/total GiBso the device's total memory isvisible.
The msm memory-type part is adapted from MangoHud PR #2073.
Behaviour
Before:
After:
Scope and caveats
msm_dpudoes not expose a device-wide GPU memory counter. TheVRAMrowtherefore reports the focused game/client's resident GPU allocations, not a
system-wide total. A true device-wide value would need a new kernel
sysfs/debugfs counter.
RAMtotal is/proc/meminfoMemTotal, i.e. kernel-usable RAM. It isslightly lower than the installed capacity because firmware and
reserved-memory regions are excluded.
VRAM keep their existing VRAM behaviour.
msm_dpuis changed; the downstreammsm_drm/kgsl path is left alone.Testing
just package mangohudbuilds with the new patchlevel 3/4 shows non-zero VRAM/PVRAM and RAM as
used/totalVerified GPU memory numbers against:
Test image:
ghcr.io/thucommix/armada:mango-report-vram-patchFiles changed
packages/mangohud/patches/0010-msm-report-gpu-memory-and-total-ram.patch—new patch
packages/mangohud/mangohud.spec— appliesPatch10packages/mangohud/PATCHES.md— documents the patch and upstream referenceReferences