power_dpm_f...rmance_level(9)
β¨ power_dpm_force_performance_level β¨
okay bestie, this page is from the Kernel API Manual, and the header is serving power_dpm_f...rmance_level(9) β yes, with the little truncated name, we love a dramatic entrance π
π¦ DESCRIPTION π¦
The amdgpu driver gives you a sysfs API for adjusting certain power-related parameters, and the file power_dpm_force_performance_level is literally the one used for this. It accepts the following arguments:
πΈ THE ARGUMENTS πΈ
autolowhighmanualprofile_standardprofile_min_sclkprofile_min_mclkprofile_peak
π auto π
When auto is selected, the driver will attempt to dynamically select the optimal power profile for current conditions in the driver. lowkey main character energy: it just handles it β¨
π low π
When low is selected, the clocks are forced to the lowest power state.
π₯ high π₯
When high is selected, the clocks are forced to the highest power state.
π manual π
When manual is selected, the user can manually adjust which power states are enabled for each clock domain via the sysfs pp_dpm_mclk, pp_dpm_sclk, and pp_dpm_pcie files, and adjust the power state transition heuristics via the pp_power_profile_mode sysfs file. you get the aux cord, bestie π«Ά
π profile_standard, profile_min_sclk, profile_min_mclk, profile_peak π
When the profiling modes are selected, clock and power gating are disabled and the clocks are set for different profiling cases. This mode is recommended for profiling specific work loads where you do not want clock or power gating for clock fluctuation to interfere with your results. itβs giving βclean lab conditionsβ π§
profile_standardsets the clocks to a fixed clock level which varies from asic to asic.profile_min_sclkforces the sclk to the lowest level.profile_min_mclkforces the mclk to the lowest level.profile_peaksets all clocks (mclk, sclk, pcie) to the highest levels.
π SEE ALSO π
Kernel file ./drivers/gpu/drm/amd/pm/amdgpu_pm.c
amdgpu_pm_dev_state_check(9)amdgpu_pm_get_access(9)amdgpu_pm_get_access_if_active(9)amdgpu_pm_put_access(9)power_dpm_state(9)pp_table(9)pp_od_clk_voltage(9)pp_features(9)pp_dpm_sclkpp_dpm_mclkpp_dpm_socclkpp_dpm_fclkpp_dpm_dcefclkpp_dpm_pcie(9)pp_power_profile_mode(9)gpu_busy_percent(9)mem_busy_percent(9)vcn_busy_percent(9)pcie_bw(9)unique_id(9)thermal_throttling_logging(9)apu_thermal_cap(9)gpu_metrics(9)smartshift_apu_power(9)smartshift_dgpu_power(9)smartshift_bias(9)board(9)baseboard_temp(9)gpuboard_temp(9)cur_node_power_limit(9)node_power(9)npm_status(9)global_ppt_resid(9)max_node_power_limit(9)baseboard_power(9)baseboard_power_limit(9)pm_policy(9)hwmon(9)fan_curve(9)acoustic_limit_rpm_threshold(9)acoustic_target_rpm_threshold(9)fan_target_temperature(9)fan_minimum_pwm(9)fan_zero_rpm_enable(9)fan_zero_rpm_stop_temperature(9)
and thatβs the whole page, bestie π signed off with source/version path ./drivers/gpu/drm/amd/pm, date October 2026, and footer page power_dpm_f...rmance_level(9) β slay, no cap π
π¦ 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