Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp150655pxb; Wed, 3 Feb 2021 01:58:14 -0800 (PST) X-Google-Smtp-Source: ABdhPJxKiwkGozF3DF6SThZoIkDtSayoqoCBV9LTA4ag7TxjsmPi+8J3195rtOE0IIjIWpJ1jmRc X-Received: by 2002:a17:907:961c:: with SMTP id gb28mr2296505ejc.393.1612346294693; Wed, 03 Feb 2021 01:58:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612346294; cv=none; d=google.com; s=arc-20160816; b=qJ2OXwNzEnxf9ihJ03Z9IRUtmPizZtOjawxaShJHd8SjG+ucYc1GJmYsWd/AqNI84E 3tMMTxZnegJVT18h6vi0NPcQqgScTu20rsMLApcux0U6DVsRiGO2w0+upO/Lt/SrP45s zixbjwRuMt2QdR2k/4JIMynn/DlJb+20SH2i9uIBh037/+YuuvuQu6LQ8V1m6WEFT5Yf vIcCfxBk+oaln4s0ZzscxBoDYd9Gj2bOr6nukJnIr2xbJ3rGDDAWbJC9mwGCljt8I9lg GVL4yQHQU4MrAKqjnYyFDZgWtBCcgFRI8YYcINOJPyNz7XJ0S2rHffg0naF6+feHyaTI 02vw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=ISw0JDWawaNim364Ab/y5upVkmg8OxS47d3uEmI20Tk=; b=DoMeCdo7vSbGNXlZE8darN1T2IpAkSTipGJgTDWBUhAkcnyJKXgbkIjumOqYUJ2UM9 VG1Qt3QYuMe89ArSS2KojRgHWddarXllYmBxv/W8Ozxl9CepDI4UQz3DvfN1+1GcdDtG Fkx32oYhoE273qP2preuKJyO5xkPf74dA1p6qGKMAJNgUx1alMCybNuWj6IvSNm6+C6M +UCYkCUsYjAIClFPdX+uWgbe29pp6Q2SmDhGQ6f6FaFgr5BZT+5Yu+0XsOaygzsJ0+aT Gn1MsLtxLKs1yzc7v55AuCJN/XNN/bxv/iT3FHvQmZD+zTFsvwqmR0btZ1n8vc8sLISz C79Q== 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 s8si982531ejd.111.2021.02.03.01.57.49; Wed, 03 Feb 2021 01:58:14 -0800 (PST) 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 S233677AbhBCJ5L (ORCPT + 99 others); Wed, 3 Feb 2021 04:57:11 -0500 Received: from mx2.suse.de ([195.135.220.15]:40616 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233614AbhBCJ47 (ORCPT ); Wed, 3 Feb 2021 04:56:59 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 65A0BAF4C; Wed, 3 Feb 2021 09:56:17 +0000 (UTC) Message-ID: <1612346175.3640.32.camel@suse.cz> Subject: Re: [PATCH v2 1/1] x86,sched: On AMD EPYC set freq_max = max_boost in schedutil invariant formula From: Giovanni Gherdovich To: "Rafael J. Wysocki" Cc: Peter Zijlstra , Borislav Petkov , Ingo Molnar , "Rafael J . Wysocki" , Viresh Kumar , Jon Grimm , Nathan Fontenot , Yazen Ghannam , Thomas Lendacky , Suthikulpanit Suravee , Mel Gorman , Pu Wen , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Michael Larabel , the arch/x86 maintainers , Linux PM , Linux Kernel Mailing List , ACPI Devel Maling List Date: Wed, 03 Feb 2021 10:56:15 +0100 In-Reply-To: References: <20210122204038.3238-1-ggherdovich@suse.cz> <20210122204038.3238-2-ggherdovich@suse.cz> <1611653310.11983.66.camel@suse.cz> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2021-02-02 at 20:11 +0100, Rafael J. Wysocki wrote: > On Tue, Feb 2, 2021 at 7:45 PM Rafael J. Wysocki wrote: > > > > On Tue, Jan 26, 2021 at 5:19 PM Giovanni Gherdovich wrote: > > > > > > > > > cpufreq core asks the driver what's the f_max. What's the answer? > > > > > > intel_pstate says: 1C > > > > Yes, unless turbo is disabled, in which case it is P0. > > BTW, and that actually is quite important, the max_freq reported by > intel_pstate doesn't matter for schedutil after the new ->adjust_perf > callback has been added, because that doesn't even use the frequency. > > So, as a long-term remedy, it may just be better to implement > ->adjust_perf in acpi_cpufreq(). Thanks for pointing this out. I agree that in the long term adding ->adjust_perf to acpi_cpufreq is the best solution. Yet for this submission, considering it's late in the 5.11 cycle, the patch I propose is a reasonable candidate: the footprint is small and it's gone through a fair amount of testing. Thanks, Giovanni