XE GT FREQUENCY MANAGEMENT(9)
π Xe GT Frequency Management β¨ β Kernel API Manual
okay so bestie, welcome to Xe GT Frequency Management(9) β the page that's all about keeping your GT frequencies in check, no cap. This component is responsible for the raw GT frequency management, including the sysfs API. π
Underneath, Xe enables GuC SLPC automated frequency management. GuC is then allowed to request PCODE any frequency between the Minimum and the Maximum selected by this component. And fr fr, it's important to highlight that PCODE is the ultimate decision maker of the actual running frequency, based on thermal and other running conditions. π₯
Xe's Freq provides a sysfs API for frequency management under the <device>/tile#/gt#/freq0/ directory. periodt. π
πΈ Read-only attributes πΈ
act_freqβ The actual resolved frequency decided by PCODE.cur_freqβ The current one requested by GuC PC to the PCODE.rpn_freqβ The Render Performance (RP) N level, which is the minimal one.rpa_freqβ The Render Performance (RP) A level, which is the achievable one. Calculated by PCODE at runtime based on multiple running conditions.rpe_freqβ The Render Performance (RP) E level, which is the efficient one. Calculated by PCODE at runtime based on multiple running conditions.rp0_freqβ The Render Performance (RP) 0 level, which is the maximum one.
πΌ Read-write attributes πΌ
min_freqβ Min frequency request.max_freqβ Max frequency request. Ifmax <= min, thenfreq_minbecomes a fixed frequency request.
Yes bestie, read-write means you can poke these. But remember PCODE still has main character energy for the actual running frequency. π
π SEE ALSO π
- Kernel file:
./drivers/gpu/drm/xe/xe_gt_freq.cβxe_gt_freq_init(9)
source ./drivers/gpu/drm/xe, version/date October 2026, page Xe GT Frequency Management(9) β catch u later bestie π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms