For at least Intel iGPUs using the xe kernel driver, and likely the i915 driver as well, nvtop reports the value from cur_freq as the actual GPU frequency when Intel uses this as the "requested frequency" and use act_freq as the "actual frequency" the GPU is currently operating at.
For better accuracy, it would be nice if nvtop could report act_freq for the GPU frequency with Intel GPUs.
I noticed this issue when comparing nvtop with qmassa.
Below is the qmassa issue where ulissesf (qmassa's developer) helped explain why I was seeing different values with each tool:
ulissesf/qmassa#35 (comment)
For at least Intel iGPUs using the
xekernel driver, and likely thei915driver as well,nvtopreports the value fromcur_freqas the actual GPU frequency when Intel uses this as the "requested frequency" and useact_freqas the "actual frequency" the GPU is currently operating at.For better accuracy, it would be nice if
nvtopcould reportact_freqfor the GPU frequency with Intel GPUs.I noticed this issue when comparing
nvtopwithqmassa.Below is the
qmassaissue where ulissesf (qmassa's developer) helped explain why I was seeing different values with each tool:ulissesf/qmassa#35 (comment)