lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 05 Nov 2020 19:17:54 +0100 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Linux PM <linux-pm@...r.kernel.org> Cc: "Rafael J. Wysocki" <rafael@...nel.org>, Viresh Kumar <viresh.kumar@...aro.org>, Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>, Zhang Rui <rui.zhang@...el.com>, LKML <linux-kernel@...r.kernel.org> Subject: [PATCH 0/2] cpufreq: intel_pstate: Handle powersave governor correctly in the passive mode with HWP Hi, Even after the changes made very recently, the handling of the powersave governor is not exactly as expected when intel_pstate operates in the "passive" mode with HWP enabled. Namely, in that case HWP is not limited to the policy min frequency, but it can scale the frequency up to the policy max limit and it cannot be constrained currently, because the governor has no way to tell the driver how much room there is for adjustments around the target frequency passed to it. For this reason, patch [1/2] introduces new policy parameters, target_min and target_max, that can be used by the governor to pass that information to the driver and modifies the powersave and peformance governors to use them. Patch [2/2] modifies intel_pstate to take them into account so as to fix the powersave governor issue, but they may be applicable for other purposes in the future (eg. if the driver is updated to pass the "desired" P-state to the HWP logic instead of just setting the HWP floor to the target one, both the powersave and performance governors will need target_min and target_max to basically work as documented). Thanks!
Powered by blists - more mailing lists