Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4085914pxv; Mon, 28 Jun 2021 21:47:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw+nQODUCo5Q9EVKC42PBR71Pc72VPd2GGOgatww9F1T1QwLuJvtRvtEYyN90K9eW3fH4RO X-Received: by 2002:a17:907:384:: with SMTP id ss4mr27808840ejb.120.1624942032789; Mon, 28 Jun 2021 21:47:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624942032; cv=none; d=google.com; s=arc-20160816; b=Y/WW3qf3ts5wqNXuzHix8PYdy1kryWv1LomGaGby9ii87aZjfrWxWB7AV03SNgO/e5 7A4hfodQxgcYQcwj+ktQqMyC7MP2QscfmSRBe/j1K2qYeye6dDjBIyeYBrCrX2rIfUn5 IJJxP8pwzjM5jHE0RqNuV2o370y9v/yQV6j2g7L/2FEmUq+7SADO1b82d+pcXlhRT+Jc 8TqEgqGdwpQIqzVpv7n165XhtjQGXYeUhcrbrhjbVfCvWUUtZT0BF6P3VznubAuGGaxD OcN2cVUPqNwfiQ3GDkF0yz9klmQKfRs0IBKlOtjDYBU77KlP/8retMYfZG3jHwSJWJdP g9qg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=FgDtIS5nzZ8aSR8Tc0jaozyyA+YsZVdTeRCKNqHLJP8=; b=Ejwm0UEI2P8xXBnylQVxRys9H+4BmDwLPrzq81JizArsUGTu1ouFUx4uYuwJNRpaWu Mkq18o2iuC8OwCWmHFkv8UpcuM1786y1bQLSuzYfcES5BmSvOzfnLYyUdH9Lwu79yLxl n3lNkrx5B+vEqkjT8BHQzBeLpX+W9J3F3LxWd++Dda7n1ZcDXI+YvbMhKVj39muBxG/S tskHE/LxlVyw6OfDt0sEEuHLmC4waggLXYRzJWtUyCq0YYNQUSz313trHRB/ZpLhibhD zPSeVQ9l/62XlUEsd4Ecp/pNJg4140cBG2sSlhMQNM5kprsbcgMaIZDzmR2XBWpZdbvV fHJg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=s+7hfDSl; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k24si16241551eds.32.2021.06.28.21.46.49; Mon, 28 Jun 2021 21:47:12 -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; dkim=pass header.i=@linaro.org header.s=google header.b=s+7hfDSl; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232011AbhF2EsA (ORCPT + 99 others); Tue, 29 Jun 2021 00:48:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57088 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229705AbhF2Er6 (ORCPT ); Tue, 29 Jun 2021 00:47:58 -0400 Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DD103C061574 for ; Mon, 28 Jun 2021 21:45:30 -0700 (PDT) Received: by mail-pg1-x533.google.com with SMTP id a2so17368217pgi.6 for ; Mon, 28 Jun 2021 21:45:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=FgDtIS5nzZ8aSR8Tc0jaozyyA+YsZVdTeRCKNqHLJP8=; b=s+7hfDSlxD/Y9a7eABn6WMMoSmQi/YCkYcPpVxgDJeowPogFtVhq8UmJPpz5h7oBm1 yjuOC+N+NcfKGIW2fa+h54NgV7wTxtPvYZxPl1bmMcx/ikaLrtup3v5AZ2M9lYH0PTt6 uG4XXUJis4pLbInL2bVnVHHO5uUzd0R/LLxnf/S+aBBAfxTxsqmHkihRV/DdToPexsmx yRzCvO6SaRB9MUIElb3fOaTRr5CtwqWiN4hEQKa+6lxjMnPQ46Oks12EdtYSuj6FKWha ybm5ch2WewxpIlUljrw9BSYI6V0rf+6O+IZodfEQC8OV5ZsjDPbVxuB8om9xkKir9LHx FJsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=FgDtIS5nzZ8aSR8Tc0jaozyyA+YsZVdTeRCKNqHLJP8=; b=fJedj8zNjMzE4V+qYJNhojWwRIxz4b5IKtGYlphIpAxyRLh2Cj7EHwckKIrha466AQ /njlcCCZoLwx3JXOyB1vn6ja533XCGyqHBfBi1VVk/qeriMTi/pcgGdI5HrkaYeXYwzQ yFgrYCWf01gTB4rAPoqHM3r0GoYM3PZz5ERfACJUNIPaRTGQxPV6C1BizipUaHRNBAxf CWf9gzLgAK3VdM/hNXUuq/s71hZXZjCDk2lx/lAISZtJWY8TQla8y5MTEuJAp1+SL/7V /tgsP7bX2SgWqJasDAoGoB5z4sl62Yx4BOXdf/JjTIyPW03UtroPz+lR/RJlhEKIpvqV ZxgA== X-Gm-Message-State: AOAM532o9TFLhtQcFgfV7qLRhbCuXgOAgWJPvQeaVQqMdxKd/vuhtxiD kaWYh4pNyeI2vznuVS8xr2uxGw== X-Received: by 2002:a63:4706:: with SMTP id u6mr26204029pga.152.1624941930251; Mon, 28 Jun 2021 21:45:30 -0700 (PDT) Received: from localhost ([136.185.134.182]) by smtp.gmail.com with ESMTPSA id p3sm1278076pjt.0.2021.06.28.21.45.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Jun 2021 21:45:29 -0700 (PDT) Date: Tue, 29 Jun 2021 10:15:27 +0530 From: Viresh Kumar To: Qian Cai Cc: Ionela Voinescu , Vincent Guittot , Rafael Wysocki , Ben Segall , Daniel Bristot de Oliveira , Dietmar Eggemann , Greg Kroah-Hartman , Ingo Molnar , Juri Lelli , Mel Gorman , Peter Zijlstra , "Rafael J. Wysocki" , Steven Rostedt , Sudeep Holla , Will Deacon , "open list:THERMAL" , ACPI Devel Maling List , linux-kernel , "Paul E. McKenney" , "Rafael J. Wysocki" Subject: Re: [PATCH V3 0/4] cpufreq: cppc: Add support for frequency invariance Message-ID: <20210629044527.puvaxcf5fxdly6tz@vireshk-i7> References: <09a39f5c-b47b-a931-bf23-dc43229fb2dd@quicinc.com> <20210623041613.v2lo3nidpgw37abl@vireshk-i7> <2c540a58-4fef-5a3d-85b4-8862721b6c4f@quicinc.com> <20210624025414.4iszkovggk6lg6hj@vireshk-i7> <20210624104734.GA11487@arm.com> <20210625102113.GB15540@arm.com> <1f83d787-a796-0db3-3c2f-1ca616eb1979@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1f83d787-a796-0db3-3c2f-1ca616eb1979@quicinc.com> User-Agent: NeoMutt/20180716-391-311a52 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25-06-21, 09:31, Qian Cai wrote: > The problem is that all CPUs are never scaling down. > "cpuinfo_cur_freq" and "scaling_cur_freq" are always the 2800 MHz on > all CPUs on this idle system. This looks like a regression somewhere > as in 5.4-based kernel, I can see "cpuinfo_cur_freq" can go down to > 2000 MHz in the same scenario. I'll bisect a bit unless you have > better ideas? Few things which may let us understand the readings properly. - cpuinfo_cur_freq: eventually makes a call to cppc_cpufreq_get_rate() and returns the *actual* frequency hardware is running at (based on counter diff around 2 us delay). - scaling_cur_freq: is the frequency the cpufreq core thinks the hardware is running at, it would more in sync with what schedutil (or other governors) wants the CPU to run at. This can be different from what the hardware is running at, i.e. given by cpuinfo_cur_freq. -- viresh