The patch titled powernow-k8: limit Pstate transition latency check has been added to the -mm tree. Its filename is powernow-k8-limit-pstate-transition-latency-check.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: powernow-k8: limit Pstate transition latency check From: Borislav Petkov <borislav.petkov@xxxxxxx> The Pstate transition latency check was added for broken F10h BIOSen which wrongly contain a value of 0 for transition and bus master latency. Fam11h and later, however, (will) have similar transition latency so extend that behavior for them too. Signed-off-by: Borislav Petkov <borislav.petkov@xxxxxxx> Cc: Dave Jones <davej@xxxxxxxxxx> Cc: Mark Langsdorf <Mark.Langsdorf@xxxxxxx> Cc: Thomas Renninger <trenn@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- arch/x86/kernel/cpu/cpufreq/powernow-k8.c | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff -puN arch/x86/kernel/cpu/cpufreq/powernow-k8.c~powernow-k8-limit-pstate-transition-latency-check arch/x86/kernel/cpu/cpufreq/powernow-k8.c --- a/arch/x86/kernel/cpu/cpufreq/powernow-k8.c~powernow-k8-limit-pstate-transition-latency-check +++ a/arch/x86/kernel/cpu/cpufreq/powernow-k8.c @@ -1025,13 +1025,12 @@ static int get_transition_latency(struct } if (max_latency == 0) { /* - * Fam 11h always returns 0 as transition latency. - * This is intended and means "very fast". While cpufreq core - * and governors currently can handle that gracefully, better - * set it to 1 to avoid problems in the future. - * For all others it's a BIOS bug. + * Fam 11h and later may return 0 as transition latency. This + * is intended and means "very fast". While cpufreq core and + * governors currently can handle that gracefully, better set it + * to 1 to avoid problems in the future. */ - if (boot_cpu_data.x86 != 0x11) + if (boot_cpu_data.x86 < 0x11) printk(KERN_ERR FW_WARN PFX "Invalid zero transition " "latency\n"); max_latency = 1; _ Patches currently in -mm which might be from borislav.petkov@xxxxxxx are linux-next.patch powernow-k8-limit-pstate-transition-latency-check.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html