diff options
author | Björn Bidar | 2022-08-15 01:41:36 +0300 |
---|---|---|
committer | Björn Bidar | 2022-08-15 01:53:06 +0300 |
commit | 0c2ed81feac01240fdc5ed571ed3b563ec0dbec2 (patch) | |
tree | 4a5ab325dfb9791e85081e2df5721c2f8dfb875b /0013-ZEN-intel-pstate-Implement-enable-parameter.patch | |
parent | 231af842c35d87c5eb9f89c268d376ca9340bdaf (diff) | |
download | aur-0c2ed81feac01240fdc5ed571ed3b563ec0dbec2.tar.gz |
Update to 5.19.1.pf2-1
- New upstream release based on 5.19.1
- Updated ZEN patches
- Drop ZEN MGLRU patch
- Sync kernel config with Arch and Arch32
Signed-off-by: Björn Bidar <bjorn.bidar@thaodan.de>
Diffstat (limited to '0013-ZEN-intel-pstate-Implement-enable-parameter.patch')
-rw-r--r-- | 0013-ZEN-intel-pstate-Implement-enable-parameter.patch | 57 |
1 files changed, 57 insertions, 0 deletions
diff --git a/0013-ZEN-intel-pstate-Implement-enable-parameter.patch b/0013-ZEN-intel-pstate-Implement-enable-parameter.patch new file mode 100644 index 000000000000..63d187b7915e --- /dev/null +++ b/0013-ZEN-intel-pstate-Implement-enable-parameter.patch @@ -0,0 +1,57 @@ +From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 +From: Steven Barrett <steven@liquorix.net> +Date: Wed, 15 Jan 2020 20:43:56 -0600 +Subject: [PATCH] ZEN: intel-pstate: Implement "enable" parameter + +If intel-pstate is compiled into the kernel, it will preempt the loading +of acpi-cpufreq so you can take advantage of hardware p-states without +any friction. + +However, intel-pstate is not completely superior to cpufreq's ondemand +for one reason. There's no concept of an up_threshold property. + +In ondemand, up_threshold essentially reduces the maximum utilization to +compare against, allowing you to hit max frequencies and turbo boost +from a much lower core utilization. + +With intel-pstate, you have the concept of minimum and maximum +performance, but no tunable that lets you define, maximum frequency +means 50% core utilization. For just this oversight, there's reasons +you may want ondemand. + +Lets support setting "enable" in kernel boot parameters. This lets +kernel maintainers include "intel_pstate=disable" statically in the +static boot parameters, but let users of the kernel override this +selection. +--- + Documentation/admin-guide/kernel-parameters.txt | 3 +++ + drivers/cpufreq/intel_pstate.c | 2 ++ + 2 files changed, 5 insertions(+) + +diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt +index 0185df52bb49883434327779aa6fc37383f9e7e4..7dd12dc178f9db6b043f0e2ab3cfa344906a1ef6 100644 +--- a/Documentation/admin-guide/kernel-parameters.txt ++++ b/Documentation/admin-guide/kernel-parameters.txt +@@ -2057,6 +2057,9 @@ + disable + Do not enable intel_pstate as the default + scaling driver for the supported processors ++ enable ++ Enable intel_pstate in-case "disable" was passed ++ previously in the kernel boot parameters + passive + Use intel_pstate as a scaling driver, but configure it + to work with generic cpufreq governors (instead of +diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c +index 57cdb36798854a941d1258b611c6e57bceddafcb..08091cfac5550a0e107a931e6ef6e625b2235cfb 100644 +--- a/drivers/cpufreq/intel_pstate.c ++++ b/drivers/cpufreq/intel_pstate.c +@@ -3540,6 +3540,8 @@ static int __init intel_pstate_setup(char *str) + + if (!strcmp(str, "disable")) + no_load = 1; ++ else if (!strcmp(str, "enable")) ++ no_load = 0; + else if (!strcmp(str, "active")) + default_driver = &intel_pstate; + else if (!strcmp(str, "passive")) |