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=-5.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,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 4B724C2D0E4 for ; Tue, 17 Nov 2020 10:47:54 +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 CA15D22447 for ; Tue, 17 Nov 2020 10:47:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="gLJq0PFN" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CA15D22447 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=arm.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-Type: Content-Transfer-Encoding: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=3FAg2nNZ7sJbdUgpYkhNGs7vY5iH6QhGCaLnHdcf/I0=; b=gLJq0PFNF3K0QguFwWyZ0myiQ GfLOv9wZcT9Xgct6PAT7V3jogHMJa5JoMfUbPteB4zse1WnATcAmQzN6VJHy68EQLvtK6oJOHPsy3 KakZEAjndtUnrBiaOtcG6nUJxah0WRV+oLE8ib7LDVY7tnOQnZccTIyTrZ1a2ZExV8t/xoNG2NmyO aDcQjiCA/V8yBP+vjBJno0BOebMNeUnQv8pTa3IM1p38cxg9z2dP1tHHZNiqioAWnFH+e+8q552wT bMgUdiYeD+664g1Ga0zQOf7+5pvKka17k7d9+qnQ/jfFvN2zT9uhGVCWBrVH71pjadRbwQBwICWdK 5bXwbt95Q==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1keyWG-0003GT-1Y; Tue, 17 Nov 2020 10:47:28 +0000 Received: from foss.arm.com ([217.140.110.172]) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1keyWD-0003Fj-8C for linux-arm-kernel@lists.infradead.org; Tue, 17 Nov 2020 10:47:26 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 69CA3D6E; Tue, 17 Nov 2020 02:47:24 -0800 (PST) Received: from [10.57.25.49] (unknown [10.57.25.49]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 206DF3F718; Tue, 17 Nov 2020 02:47:20 -0800 (PST) Subject: Re: [PATCH v3 3/3] [RFC] CPUFreq: Add support for cpu-perf-dependencies To: Viresh Kumar References: <20201102120115.29993-1-nicola.mazzucato@arm.com> <20201102120115.29993-4-nicola.mazzucato@arm.com> <20201106092020.za3oxg7gutzc3y2b@vireshk-i7> <0a334a73-45ef-58ff-7dfd-9df6f4ff290a@arm.com> <20201106105514.bhtdklyhn7goml64@vireshk-i7> <7f73bcd6-0f06-4ef0-7f02-0751e6c4d94b@arm.com> <20201109065742.22czfgyjhsjmkytf@vireshk-i7> <2fa8a5c0-f66d-34bc-7f1c-8462e7532e0a@arm.com> <20201117101128.6uapqg56arwqmm5p@vireshk-i7> From: Lukasz Luba Message-ID: <117c6d30-0013-7222-dedb-57e65ba84d15@arm.com> Date: Tue, 17 Nov 2020 10:47:19 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20201117101128.6uapqg56arwqmm5p@vireshk-i7> Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201117_054725_409544_AD65ACA3 X-CRM114-Status: GOOD ( 21.61 ) 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: nm@ti.com, devicetree@vger.kernel.org, linux-pm@vger.kernel.org, sboyd@kernel.org, vireshk@kernel.org, daniel.lezcano@linaro.org, rjw@rjwysocki.net, linux-kernel@vger.kernel.org, robh+dt@kernel.org, Nicola Mazzucato , sudeep.holla@arm.com, chris.redpath@arm.com, morten.rasmussen@arm.com, linux-arm-kernel@lists.infradead.org Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 11/17/20 10:11 AM, Viresh Kumar wrote: > On 16-11-20, 11:33, Lukasz Luba wrote: >> On 11/9/20 6:57 AM, Viresh Kumar wrote: >>> On 06-11-20, 11:14, Lukasz Luba wrote: >>>> I also had similar doubts, because if we make frequency requests >>>> independently for each CPU, why not having N cooling devs, which >>>> will set independently QoS max freq for them... >>>> >>>> What convinced me: >>>> EAS and FIE would know the 'real' frequency of the cluster, IPA >>>> can use it also and have only one cooling device per cluster. >>>> >>>> We would like to keep this old style 'one cooling device per cpuset'. >>>> I don't have strong opinion and if it would appear that there are >>>> some errors in freq estimation for cluster, then maybe it does make >>>> more sense to have cdev per CPU... >>> >>> Let me rephrase my question. What is it that doesn't work _correctly_ >>> with cdev per cpufreq policy in your case? What doesn't work well if >>> the thermal stuff keeps looking at only the related_cpus thing and not >>> the cpu-perf-dependencies thing? >>> >> >> We don't have a platform which would be this per-cpu freq request, yet. >> Thus it's hard to answer your question. The EAS would work in 'old >> style' - cluster mode. I don't know how IPA would work on such HW >> and SW configuration. To figure this out I need a real platform. > > Hmm, so who are going to be the users of this new stuff (dependent > CPUs) ? I don't think cpufreq-cooling should be updated, unless there > is a compelling reason to. Fair enough. What if we come back with experiments results in future? Currently we are trying to conduct experiments with Nicola on modified Juno firmware and kernel) > > The other one in energy model ? Why does it need this information ? The energy model needs this information, because it's used during the sched domain re-build. The sched domain is then used in the EAS main functions: feec() [1] and compute_energy() [2]. What EAS normally does is 'trying different options to put a task on different CPUs and observe the potential energy costs'. Example, we need the 'cluster' frequency, because when you put a task on a CPU its freq might need to be set a bit higher. This would affect all CPUs in the cluster not only one and we capture that energy cost. Then, we try to put a task on other CPU in that cluster and if it appears to be no need of rising freq for the whole cluster, then it wins. > > Who else ? > FIE.. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel