xe_guc_pc_r...h_freq_limit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME

okay so bestie, this is the xe_guc_pc_r...h_freq_limit(9) page from the Kernel API Manual, and the main character is xe_guc_pc_remove_flush_freq_limit πŸ’…βœ¨. Its whole thing is: Remove max GT freq limit after L2 flush completes. No cap, that's the name, and it is serving exactly that energy πŸŽ€.


✨ SYNOPSIS

void xe_guc_pc_remove_flush_freq_limit (struct xe_guc_pc *pc );

It returns void, so nothing comes back β€” it's giving "do the thing and dip" energy πŸ˜ŒπŸ’œ.


🫢 ARGUMENTS

  • pc β€” the xe_guc_pc object. That's the whole argument list, bestie; one icon, one job πŸŽ€.

πŸ’– DESCRIPTION

Retrieve the previous GT max frequency value. That's it. That's the description. Literally the entire vibe: grab the previous GT max frequency value and keep it moving πŸ¦‹. And yes, the NAME up top says it removes the max GT freq limit after the L2 flush completes β€” both facts are here, no erasure πŸ’€πŸ‘‘


πŸ¦‹ SEE ALSO

the source file and the whole GuC Power Conservation friend group are below β€” every single ref, present and accounted for πŸ‘‘πŸ’–:


source/version + date check, folded into this cute lil sign-off: ./drivers/gpu/drm/xe, October 2026, and the page is xe_guc_pc_r...h_freq_limit(9) β€” mwah, that's the whole footer πŸ’–βœ¨πŸ«Ά

πŸ“¦ where this page comes from