[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210513075930.22657-1-ggherdovich@suse.cz>
Date: Thu, 13 May 2021 09:59:30 +0200
From: Giovanni Gherdovich <ggherdovich@...e.cz>
To: "Rafael J . Wysocki" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Len Brown <lenb@...nel.org>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Giovanni Gherdovich <ggherdovich@...e.cz>
Subject: [PATCH] cpufreq: intel_pstate: Force intel_pstate to load when HWP disabled in firmware
On CPUs succeeding SKX, eg. ICELAKE_X, intel_pstate doesn't load unless
CPUID advertises support for the HWP feature. Some OEMs, however, may offer
users the possibility to disable HWP from the BIOS config utility by
altering the output of CPUID.
Add the command line option "intel_pstate=hwp_broken_firmware" so that
intel_pstate still loads in that case, providing OS-driven frequency
scaling.
Signed-off-by: Giovanni Gherdovich <ggherdovich@...e.cz>
---
Documentation/admin-guide/kernel-parameters.txt | 7 +++++++
Documentation/admin-guide/pm/intel_pstate.rst | 7 +++++++
drivers/cpufreq/intel_pstate.c | 7 ++++++-
3 files changed, 20 insertions(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index cb89dbdedc46..278ec0718dc9 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -1951,6 +1951,13 @@
per_cpu_perf_limits
Allow per-logical-CPU P-State performance control limits using
cpufreq sysfs interface
+ hwp_broken_firmware
+ Register intel_pstate as the scaling driver despite the
+ hardware-managed P-states (HWP) feature being disabled in
+ firmware. On CPU models succeeding SKX, intel_pstate expects
+ HWP to be supported. Some OEMs may use firmware that hides the
+ feature from the OS. With this option intel_pstate will
+ load regardless.
intremap= [X86-64, Intel-IOMMU]
on enable Interrupt Remapping (default)
diff --git a/Documentation/admin-guide/pm/intel_pstate.rst b/Documentation/admin-guide/pm/intel_pstate.rst
index df29b4f1f219..1e6f139d5b05 100644
--- a/Documentation/admin-guide/pm/intel_pstate.rst
+++ b/Documentation/admin-guide/pm/intel_pstate.rst
@@ -689,6 +689,13 @@ of them have to be prepended with the ``intel_pstate=`` prefix.
Use per-logical-CPU P-State limits (see `Coordination of P-state
Limits`_ for details).
+``hwp_broken_firmware``
+ Register ``intel_pstate`` as the scaling driver despite the
+ hardware-managed P-states (HWP) feature being disabled in firmware.
+
+ On CPU models succeeding SKX, ``intel_pstate`` expects HWP to be
+ supported. Some OEMs may use firmware that hides the feature from the
+ OS. With this option ``intel_pstate`` will load regardless.
Diagnostics and Tuning
======================
diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
index f0401064d7aa..8635251f86f2 100644
--- a/drivers/cpufreq/intel_pstate.c
+++ b/drivers/cpufreq/intel_pstate.c
@@ -2856,6 +2856,7 @@ static int intel_pstate_update_status(const char *buf, size_t size)
static int no_load __initdata;
static int no_hwp __initdata;
static int hwp_only __initdata;
+static int hwp_broken_firmware __initdata;
static unsigned int force_load __initdata;
static int __init intel_pstate_msrs_not_valid(void)
@@ -3066,7 +3067,7 @@ static int __init intel_pstate_init(void)
}
} else {
id = x86_match_cpu(intel_pstate_cpu_ids);
- if (!id) {
+ if (!id && !hwp_broken_firmware) {
pr_info("CPU model not supported\n");
return -ENODEV;
}
@@ -3149,6 +3150,10 @@ static int __init intel_pstate_setup(char *str)
force_load = 1;
if (!strcmp(str, "hwp_only"))
hwp_only = 1;
+ if (!strcmp(str, "hwp_broken_firmware")) {
+ pr_info("HWP disabled by firmware\n");
+ hwp_broken_firmware = 1;
+ }
if (!strcmp(str, "per_cpu_perf_limits"))
per_cpu_limits = true;
--
2.26.2
Powered by blists - more mailing lists