Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp522066pxa; Tue, 11 Aug 2020 08:36:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwc2D+MNzcA5hnnvAb5e0w9rE0ZhSg6lNV2T9mX9t4VXb7Ft7E0E+OMJ3JRf2aL5TYqkMOM X-Received: by 2002:a17:906:68e:: with SMTP id u14mr28566307ejb.166.1597160215729; Tue, 11 Aug 2020 08:36:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597160215; cv=none; d=google.com; s=arc-20160816; b=dS8u0d9ztLhRw7v3kt90N52SR6jWdC212FNmVJq3Z+8H4giavdiat7AEYub7Gv6AtE UA+B3Lk+jOr6an3OLZhI0O5BQJjeZK12aSYnvEDTpcALdhE26Uk5YduOl4WkPfwroyot bCxteQ1hxryfH1Qpnn9QSMW/eQnMFj8GcxnGRcApjeHCeM/pmuFORC8baKyVpr9zdLG0 OrYDutLnDcoPjuaH5yYn+kSuMRJHqoBA2BZr40eAJXrLixZ8yh4QEKpyXHdDElVdKtmY bxt+R4uWSpHRUZLFxjsWeXbhaymr7gHfj/arvkAr97O0CwMECJRUuiZooTenM4BRHn1v NXWg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=bof4nHh05InSjw3W5cUE7d608mpVjDivohYrBsD0WZo=; b=f4IENgR3eLMWBPiKPymRrqZbIanj/HF8f1uVgBx8fr6vp2c0kCD98Lbx2uBWhb7F6Z mt5S0d03OiM3EgVSwLyvDfZg7jJzKPMeyd11AuyZg6Pall4K+NFD8WI+Ef0YwXzVJr0f YYeuHpTMN9ZMgvGrudxjNHSI1pRwuZo2WXz+SuK9VJq0ClbOSDytYALf/zN/CKve8PN1 g/U5vB7TAIGo/7dn3TM1WziN0rNV8Rc527mW+sDvGnibC4kKQCSbekO3aR5LH2T8jPwp KZkVNhIb6iXFflsqoX7XqCB3LzbpTUOGJ+iWXk9fx1qQJAVaRhSjMvMJ/Jv+9KTWqqen dz+Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u12si1757728edd.121.2020.08.11.08.36.32; Tue, 11 Aug 2020 08:36:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729055AbgHKPdx (ORCPT + 99 others); Tue, 11 Aug 2020 11:33:53 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:62204 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728859AbgHKPdw (ORCPT ); Tue, 11 Aug 2020 11:33:52 -0400 Received: from 89-64-89-44.dynamic.chello.pl (89.64.89.44) (HELO kreacher.localnet) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83.415) id 2461079d11a94e2c; Tue, 11 Aug 2020 17:33:50 +0200 From: "Rafael J. Wysocki" To: Francisco Jerez Cc: Linux PM , Linux Documentation , LKML , Peter Zijlstra , Srinivas Pandruvada , Giovanni Gherdovich , Doug Smythies , Viresh Kumar Subject: Re: [PATCH v7] cpufreq: intel_pstate: Implement passive mode with HWP enabled Date: Tue, 11 Aug 2020 17:33:49 +0200 Message-ID: <4931766.VNY61sLD3B@kreacher> In-Reply-To: <87mu32atsy.fsf@riseup.net> References: <4981405.3kqTVLv5tO@kreacher> <122847018.uQ7iJ9lzrg@kreacher> <87mu32atsy.fsf@riseup.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, August 11, 2020 2:51:41 AM CEST Francisco Jerez wrote: > > --==-=-= > Content-Type: multipart/mixed; boundary="=-=-=" > > --=-=-= > Content-Type: text/plain; charset=utf-8 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > "Rafael J. Wysocki" writes: > > > From: Rafael J. Wysocki > > > > Allow intel_pstate to work in the passive mode with HWP enabled and > > make it set the HWP minimum performance limit (HWP floor) to the > > P-state value given by the target frequency supplied by the cpufreq > > governor, so as to prevent the HWP algorithm and the CPU scheduler > > from working against each other, at least when the schedutil governor > > is in use, and update the intel_pstate documentation accordingly. > > > > Among other things, this allows utilization clamps to be taken > > into account, at least to a certain extent, when intel_pstate is > > in use and makes it more likely that sufficient capacity for > > deadline tasks will be provided. > > > > After this change, the resulting behavior of an HWP system with > > intel_pstate in the passive mode should be close to the behavior > > of the analogous non-HWP system with intel_pstate in the passive > > mode, except that in the frequency range below the base frequency > > (ie. the frequency retured by the base_frequency cpufreq attribute > > in sysfs on HWP systems) the HWP algorithm is allowed to make the > > CPU run at a frequency above the floor P-state set by intel_pstate, > > with or without hardware coordination of P-states among CPUs in the > > same package. > > > > The "frequency range below the base frequency" part of the paragraph > above seems somewhat misleading, since AFAICT the same thing will happen > in the P-state range above the base frequency. Fair enough. I rephrased the changelog when applying the patch. > Another minor comment below, other than that LGTM: And this one has been fixed too. > Reviewed-by: Francisco Jerez Thanks!