https://bugzilla.kernel.org/show_bug.cgi?id=19702 Thomas Renninger <trenn@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DOCUMENTED --- Comment #50 from Thomas Renninger <trenn@xxxxxxx> 2010-11-10 12:51:11 --- > Will the scheduler adapt to the changed cpu features with only that single > change? Yes, the only part I found using it always checks for: if (has_cpu_cap(X86_FEATURE_APERFMPERF)) use_it() So unsetting the cap effectively disables usage there on the next schedule. This may change in the future, as said it's a hack... Perfect would be a boot param disbable_cpu_cap=xy, but as most of these caps are evaluated early it's hard to implement. vyncere: Looks like Linux works correctly according to your BIOS settings :) Not sure whether I should set this invalid. I set it documented, if there are more machines with broken aperf/mperf timers, they might find it and if this should be a more common issue, it still can be thought of a fix/workaround for the kernel. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
