XE GT FREQUENCY MANAGEMENT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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. If max <= min, then freq_min becomes 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 πŸ”—


source ./drivers/gpu/drm/xe, version/date October 2026, page Xe GT Frequency Management(9) β€” catch u later bestie πŸ’–

πŸ“¦ where this page comes from