3 ms·
Really? Maybe I'm thinking of a different tool then, because that didn't work for me (on an AMD CPU)
by SCdF 7y ago
Really? Maybe I'm thinking of a different tool then, because that didn't work for me (on an AMD CPU)
- signa11 7y agooh, that's surprising, here is what i did: seldon ~ # cpupower frequency-set -f 1.86GHz Setting cpu: 0 Setting cpu: 1 Setting cpu: 2 Setting cpu: 3 Setting cpu: 4 Setting cpu: 5 Setting cpu: 6 Setting cpu: 7 seldon ~ # cpupower --cpu all frequency-info | grep -E '^analyzing CPU.*|current CPU frequency' analyzing CPU 0: current CPU frequency: 1.86 GHz (asserted by call to hardware) analyzing CPU 1: current CPU frequency: 1.86 GHz (asserted by call to hardware) analyzing CPU 2: current CPU frequency: 1.86 GHz (asserted by call to hardware) analyzing CPU 3: current CPU frequency: 1.86 GHz (asserted by call to hardware) analyzing CPU 4: current CPU frequency: 1.86 GHz (asserted by call to hardware) analyzing CPU 5: current CPU frequency: 1.86 GHz (asserted by call to hardware) analyzing CPU 6: current CPU frequency: 1.86 GHz (asserted by call to hardware) analyzing CPU 7: current CPU frequency: 1.86 GHz (asserted by call to hardware) this an oldish Intel(R) Core(TM) i7 CPU. just tried it on an odroid, and it seems to do the right thing there as well.