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=-7.0 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 728B6C433E0 for ; Tue, 4 Aug 2020 17:28:31 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 454B9206C0 for ; Tue, 4 Aug 2020 17:28:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="2iJpu4mg"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="I+mdW542" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 454B9206C0 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=RRJK/G0WzXpZKpXaACYk8cvx0jEnfrDZ/e/3B6Z4odg=; b=2iJpu4mguDwaEc/WSMfYgtaUQ BAkRCPkK9ezogeSP4ZEYnnGpcmCLc3nNwnuiu9Yhcw/k3wAZ6BoVuTqPI0jWMQtGdHWrbtFzuFJaS DO/tmbYrdYQ0kL4L+nYhE8bY5m97AMCems0SAiRHZ5A2Ynq1yjbiKXAdK69CirbRxRwQoW0nFucgR nGead5I1lcAI+taWuEPpBpJIQs+89iyV9Fam79sPBXhUPYKza218mWuVhaI3wz1XMKswrSM5w+vLI xTLDlmDeaR2G3Z2KahPG3aMmq009tMGnIRvCHC+wOc8Sc9M9fBQhIrCDAx7UUWCdG1R+mb0aPos9Y TGxwwCdAQ==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k30if-0001tG-KV; Tue, 04 Aug 2020 17:27:21 +0000 Received: from mail-qk1-x743.google.com ([2607:f8b0:4864:20::743]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k30ic-0001sQ-Ib for linux-arm-kernel@lists.infradead.org; Tue, 04 Aug 2020 17:27:19 +0000 Received: by mail-qk1-x743.google.com with SMTP id x69so39162443qkb.1 for ; Tue, 04 Aug 2020 10:27:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=E7NJIozHt+m1AVrlcoRDMsMHIksDQclStBIFbmvuAkE=; b=I+mdW542d7UOQfbeQJP/xjlQS1tov89CwInKPql8afcySHNrxANla/IQ76zu+0vh+B ocIruu8EMGqEnbySc/94Q5F0J7FN2cWZC09Jn0k36n3TLJXu2zTO5kaYG70ewnYvIFQl oacmZIKAjDj2PE/N/6nwub/4GvL1aycYrNUjlznbAnvHHAx77PUI3nMq+sakBumRB0I7 dfO99hCh2yD8RHc92ez5ogHWP2E66Kp2zEpS2Lc6VNlntAFmeAUW3p6coovgX21b22st /+20oVsjjQmJ54B89iZ0WhoSjDF5TLRtieHX3VXl9dFGmtpwriKFQpUYX/873OXfi+sp xJZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=E7NJIozHt+m1AVrlcoRDMsMHIksDQclStBIFbmvuAkE=; b=mWWs6W+VvIUsy1uq14vJihkYWiv7Xi14Cm2OftggFcc9X5buFpH2b3GOcjasmjlCH7 1+BUUahc9MC27jDtxBvG4JtFeON9psVwTIRLga4/B40+bA25BO7R7VrQw2yVV157y1bd gOLkEfmdVGF/qQrLULWB0evARi+ZzwOXf2gew+vw1Wk+5MocmvQS3y2LXrrXZ71F9kBN GsFZh1v5cM1D1vbPaL+ra0HXwunA6v05MZRPHGt1mW4tb9FUdzwQnusSQMvCTFexTadN 9tIJUtBoxRua1j8LMN7dRw+QDqdUFDOqu6lO6UOUCmItBnbwxfeqCUvC/NO7hsbbSjVn Uoyg== X-Gm-Message-State: AOAM531QMfH3ChbFA+iguRm1w+FcqPBiXUqEiRU1UGUl8WjxA6s8ocyJ F2EJneLdkJyfg7HpzzPunZg= X-Google-Smtp-Source: ABdhPJxgOgWsiwGqnjZGd25tRAK+Z9iymVMCZxbhUXOhQX8Mw02dqjnCrEFAua62Drkm4YgBGJ1FTw== X-Received: by 2002:a05:620a:234:: with SMTP id u20mr21352090qkm.54.1596562036752; Tue, 04 Aug 2020 10:27:16 -0700 (PDT) Received: from [192.168.1.3] (ip68-111-84-250.oc.oc.cox.net. [68.111.84.250]) by smtp.gmail.com with ESMTPSA id 71sm22970285qkk.125.2020.08.04.10.27.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Aug 2020 10:27:15 -0700 (PDT) Subject: Re: [PATCH 0/4] CPUFreq statistics retrieved by drivers To: Lukasz Luba , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org References: <20200729151208.27737-1-lukasz.luba@arm.com> From: Florian Fainelli Message-ID: Date: Tue, 4 Aug 2020 10:27:13 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200729151208.27737-1-lukasz.luba@arm.com> Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200804_132718_814204_0A4E85DD X-CRM114-Status: GOOD ( 17.72 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: viresh.kumar@linaro.org, rjw@rjwysocki.net, cristian.marussi@arm.com, sudeep.holla@arm.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 7/29/2020 8:12 AM, Lukasz Luba wrote: > Hi all, > > The existing CPUFreq framework does not tracks the statistics when the > 'fast switch' is used or when firmware changes the frequency independently > due to e.g. thermal reasons. However, the firmware might track the frequency > changes and expose this to the kernel. Or the firmware might have changed the CPU frequency in response to a request from the secure world for instance. > > This patch set aims to introduce CPUfreq statistics gathered by firmware > and retrieved by CPUFreq driver. It would require a new API functions > in the CPUFreq, which allows to poke drivers to get these stats. >From a debugging perspective, it would be helpful if the firmware maintained statistics were exposed as a super-set of the Linux cpufreq statistics and aggregated into them such that you could view the normal world vs. secure world residency of a given frequency point. This would help because a lot of times, Linux requests freq X, but the secure world requires freq Y (with X >= Y) and people do not really understand why the resulting power usage is higher for instance. What are your thoughts on this? -- Florian _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel