Comment 13 for bug 2026658

Nope, running stress -c 2 yields...

long_term_power starts at 65, drops to ~10, then jumps around values like 37.625, 30.0, 31.0, 28.0, but then after a ~minute the power values look like this and clearly aren't recovering:

{'backup_rest': 281474976776192,
 'locked': False,
 'long_term_enabled': True,
 'long_term_power': 3.0,
 'long_term_time': 28.0,
 'short_term_enabled': True,
 'short_term_power': 160.0,
 'short_term_time': 0.00244140625}

grep looks like this:
/sys/devices/system/cpu/intel_pstate/hwp_dynamic_boost:0
/sys/devices/system/cpu/intel_pstate/max_perf_pct:100
/sys/devices/system/cpu/intel_pstate/min_perf_pct:10
/sys/devices/system/cpu/intel_pstate/no_turbo:0
/sys/devices/system/cpu/intel_pstate/status:active

CPU speeds are set to their nominal speeds but immediately drop down to 400mhz as soon as they take any load.

A more real-world check of a parallel test suite I run frequently and know should take on the order of 3.5 seconds takes 30. (Running it in single threaded is clearly also terrible but I don't offhand know its normal run time.)