diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-26 20:14:30 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-26 20:14:30 -0500 |
| commit | 9a91f00699d770ff7bd0e9aa4ecee1533351b41c (patch) | |
| tree | 1751083cd49dc782f9e74d8509332734e90e02c9 /scripts/testing/lib/vm-utils.sh | |
| parent | b5208340baa5896ce9f69081b1ead30f20e85b9a (diff) | |
| download | archsetup-9a91f00699d770ff7bd0e9aa4ecee1533351b41c.tar.gz archsetup-9a91f00699d770ff7bd0e9aa4ecee1533351b41c.zip | |
fix(archsetup): remove the cpupower setup, wrong for this hardware
I added cpupower earlier this session, VM-verified it, then realized it's the wrong tool here. Both my machines run active-mode pstate drivers (the desktop on amd-pstate-epp, the laptop on intel_pstate), where the only governors are performance and powersave and the driver scales frequency itself via EPP. Both already sit on powersave, which is the recommended adaptive mode, not "slow."
cpupower's governor-forcing only helps older acpi-cpufreq systems, which I don't run. Forcing performance would pin max clocks: worse battery on the laptop, pointless heat on the desktop. So I dropped the cpupower step rather than ship a backwards default. The cpufreq drivers self-manage with no help from us.
Diffstat (limited to 'scripts/testing/lib/vm-utils.sh')
0 files changed, 0 insertions, 0 deletions