Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755509Ab3CEWPr (ORCPT ); Tue, 5 Mar 2013 17:15:47 -0500 Received: from mail-pb0-f54.google.com ([209.85.160.54]:50111 "EHLO mail-pb0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755203Ab3CEWPk (ORCPT ); Tue, 5 Mar 2013 17:15:40 -0500 From: dirk.brandewie@gmail.com To: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org Cc: konrad.wilk@oracle.com, jwboyer@redhat.com, Dirk Brandewie , Dirk Brandewie Subject: [PATCH 1/2] cpufreq/intel_pstate: Do not load on VM that do not report max P state. Date: Tue, 5 Mar 2013 14:15:26 -0800 Message-Id: <1362521727-20666-2-git-send-email-dirk.brandewie@gmail.com> X-Mailer: git-send-email 1.7.7.6 In-Reply-To: <1362521727-20666-1-git-send-email-dirk.brandewie@gmail.com> References: <1362521727-20666-1-git-send-email-dirk.brandewie@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1144 Lines: 35 From: Dirk Brandewie It seems some VMs support the P state MSRs but return zeros. Fail gracefully if we are running in this environment. https://bugzilla.redhat.com/show_bug.cgi?id=916833 Reported-by: jwboyer@redhat.com Signed-off-by: Dirk Brandewie --- drivers/cpufreq/intel_pstate.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c index 096fde0..2bfd083 100644 --- a/drivers/cpufreq/intel_pstate.c +++ b/drivers/cpufreq/intel_pstate.c @@ -662,6 +662,9 @@ static int intel_pstate_set_policy(struct cpufreq_policy *policy) cpu = all_cpu_data[policy->cpu]; + if (!policy->cpuinfo.max_freq) + return -ENODEV; + intel_pstate_get_min_max(cpu, &min, &max); limits.min_perf_pct = (policy->min * 100) / policy->cpuinfo.max_freq; -- 1.7.7.6 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/