Remove the nv_perf_level config option and figure it out programmatically

This also fixes the instances in testing where we don't have the nv overclock in use, but we do have the mode set

	Solves issues explaining the what the perf_level actually meant, and future proofs for any PR that wants to set individual perf levels
This commit is contained in:
Marc Di Luzio
2019-03-10 15:11:24 +00:00
parent 873d0a224b
commit fec32ac53d
7 changed files with 105 additions and 104 deletions

View File

@ -53,11 +53,8 @@ inhibit_screensaver=1
; See NV_CTRL_GPU_POWER_MIZER_MODE and friends in https://github.com/NVIDIA/nvidia-settings/blob/master/src/libXNVCtrl/NVCtrl.h
;nv_powermizer_mode=1
; This corresponds to the performance level to edit in nvidia-xconfig
; Set this to the highest level shown in the nvidia settings power mizer settings
; Or from the command line check the highest perf value listed by "nvidia-settings -q [gpu:0]/GPUPerfModes"
;nv_perf_level=1
; (these two are Mhz offsets from the baseline, ie. 0 applies no change)
; These will modify the core and mem clocks of the highest perf state in the Nvidia PowerMizer
; They are measured as Mhz offsets from the baseline, 0 will reset values to default, -1 or unset will not modify values
;nv_core_clock_mhz_offset=0
;nv_mem_clock_mhz_offset=0