Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754335AbdLLNid (ORCPT ); Tue, 12 Dec 2017 08:38:33 -0500 Received: from mail-wr0-f194.google.com ([209.85.128.194]:37290 "EHLO mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754139AbdLLNia (ORCPT ); Tue, 12 Dec 2017 08:38:30 -0500 X-Google-Smtp-Source: ACJfBotQaP7kaCO2Pf18Zq+kNgUWBOWdU2F7miW90aH4FPPO585a57wp79bgrUGqoSo+p0TawD1Pgg== Date: Tue, 12 Dec 2017 14:38:24 +0100 From: Juri Lelli To: Viresh Kumar Cc: Patrick Bellasi , linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, Ingo Molnar , Peter Zijlstra , "Rafael J . Wysocki" , Vincent Guittot , Dietmar Eggemann , Morten Rasmussen , Todd Kjos , Joel Fernandes Subject: Re: [PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter Message-ID: <20171212133824.GH4635@localhost.localdomain> References: <20171130114723.29210-1-patrick.bellasi@arm.com> <20171130114723.29210-2-patrick.bellasi@arm.com> <20171207050135.vvhqttazumjg7n7n@vireshk-mac-ubuntu> <20171207124510.GP31247@e110439-lin> <20171212113727.GO25177@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171212113727.GO25177@vireshk-i7> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1971 Lines: 53 Hi Viresh, On 12/12/17 17:07, Viresh Kumar wrote: [...] > From: Viresh Kumar > Date: Tue, 12 Dec 2017 15:43:26 +0530 > Subject: [PATCH] sched: Keep track of cpufreq utilization update flags > > Currently the schedutil governor overwrites the sg_cpu->flags field on > every call to the utilization handler. It was pretty good as the initial > implementation of utilization handlers, there are several drawbacks > though. > > The biggest drawback is that the sg_cpu->flags field doesn't always > represent the correct type of tasks that are enqueued on a CPU's rq. For > example, if a fair task is enqueued while a RT or DL task is running, we > will overwrite the flags with value 0 and that may take the CPU to lower > OPPs unintentionally. There can be other corner cases as well which we > aren't aware of currently. > > This patch changes the current implementation to keep track of all the > task types that are currently enqueued to the CPUs rq. There are two > flags for every scheduling class now, one to set the flag and other one > to clear it. The flag is set by the scheduling classes from the existing > set of calls to cpufreq_update_util(), and the flag is cleared when the > last task of the scheduling class is dequeued. For now, the util update > handlers return immediately if they were called to clear the flag. > > We can add more optimizations over this patch separately. > > The last parameter of sugov_set_iowait_boost() is also dropped as the > function can get it from sg_cpu anyway. > > Signed-off-by: Viresh Kumar [...] > @@ -655,7 +669,7 @@ static int sugov_start(struct cpufreq_policy *policy) > memset(sg_cpu, 0, sizeof(*sg_cpu)); > sg_cpu->cpu = cpu; > sg_cpu->sg_policy = sg_policy; > - sg_cpu->flags = SCHED_CPUFREQ_RT; > + sg_cpu->flags = 0; > sg_cpu->iowait_boost_max = policy->cpuinfo.max_freq; > } Why this change during initialization? Thanks, - Juri