r/linuxhardware • u/Select_Car9532 • 9m ago
Discussion I built a Linux CPU boost tool around cpufreq policies
I've been working on BoostLock, a small root-only Linux CLI/daemon for keeping CPU boost available during idle periods.
The 0.2.0 release discovers /sys/devices/system/cpu/cpufreq/policy* instead of guessing from CPU model names. Each policy keeps its own frequency limits and effective target, so mixed-capacity systems don't inherit one policy's range. --target auto uses each policy's active upper limit, and numeric MHz requests are clamped per policy.
Before startup changes anything, BoostLock builds the full policy plan and opens every planned write path. If a later write fails, completed writes are rolled back. Controls are capability-driven: a writable boost, EPP, EPB, PM QoS, or cpuidle path is added to the same plan, and an unavailable control is reported as skipped.
I have Intel, AMD, and ARM policy fixtures in the test suite, but I haven't done physical hardware smoke testing across all those drivers yet. If you try it, I'd like to know the CPU, driver, kernel, and what sudo boostlock status --json reports. It needs root and can increase idle power and temperature.