From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AE6EEC55ABD for ; Tue, 10 Nov 2020 17:28:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 646E820781 for ; Tue, 10 Nov 2020 17:28:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730959AbgKJR2Z (ORCPT ); Tue, 10 Nov 2020 12:28:25 -0500 Received: from cloudserver094114.home.pl ([79.96.170.134]:48720 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730845AbgKJR2Y (ORCPT ); Tue, 10 Nov 2020 12:28:24 -0500 Received: from 89-64-88-129.dynamic.chello.pl (89.64.88.129) (HELO kreacher.localnet) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83.520) id 9ecaaf740a3def68; Tue, 10 Nov 2020 18:28:21 +0100 From: "Rafael J. Wysocki" To: Linux PM Cc: "Rafael J. Wysocki" , Viresh Kumar , Srinivas Pandruvada , Zhang Rui , LKML , Doug Smythies Subject: [PATCH v3 0/4] cpufreq: intel_pstate: Handle powersave governor correctly in the passive mode with HWP Date: Tue, 10 Nov 2020 18:21:56 +0100 Message-ID: <11312387.r5AVKgp8zO@kreacher> In-Reply-To: <13269660.K2JYd4sGFX@kreacher> References: <13269660.K2JYd4sGFX@kreacher> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org Hi, On Monday, November 9, 2020 5:49:49 PM CET Rafael J. Wysocki wrote: > > 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 there are no provisions for that in the framework. > > To address that, patches [1-3/4] add a new governor flag to indicate that this > governor wants the target frequency to be set to the exact value passed to the > driver, if possible, and change the powersave and performance governors to have > that flag set. > > The last patch makes intel_pstate take that flag into account when programming > the HWP Request MSR. The v3 simply uses different names for the new governor flags. Thanks!