Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751917AbdCCI6x (ORCPT ); Fri, 3 Mar 2017 03:58:53 -0500 Received: from mail-pg0-f46.google.com ([74.125.83.46]:33553 "EHLO mail-pg0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751657AbdCCI5v (ORCPT ); Fri, 3 Mar 2017 03:57:51 -0500 Date: Fri, 3 Mar 2017 14:01:45 +0530 From: Viresh Kumar To: Patrick Bellasi Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, Steven Rostedt , Vincent Guittot , John Stultz , Juri Lelli , Todd Kjos , Tim Murray , Andres Oportus , Joel Fernandes , Morten Rasmussen , Dietmar Eggemann , Chris Redpath , Ingo Molnar , Peter Zijlstra , "Rafael J . Wysocki" Subject: Re: [PATCH 3/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks Message-ID: <20170303083145.GA8206@vireshk-i7> References: <1488469507-32463-1-git-send-email-patrick.bellasi@arm.com> <1488469507-32463-4-git-send-email-patrick.bellasi@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1488469507-32463-4-git-send-email-patrick.bellasi@arm.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1260 Lines: 33 On 02-03-17, 15:45, Patrick Bellasi wrote: > diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c > @@ -293,15 +305,29 @@ static void sugov_update_shared(struct update_util_data *hook, u64 time, > if (curr == sg_policy->thread) > goto done; > > + /* > + * While RT/DL tasks are running we do not want FAIR tasks to > + * overwrite this CPU's flags, still we can update utilization and > + * frequency (if required/possible) to be fair with these tasks. > + */ > + rt_mode = task_has_dl_policy(curr) || > + task_has_rt_policy(curr) || > + (flags & SCHED_CPUFREQ_RT_DL); > + if (rt_mode) > + sg_cpu->flags |= flags; > + else > + sg_cpu->flags = flags; This looks so hacked up :) Wouldn't it be better to let the scheduler tell us what all kind of tasks it has in the rq of a CPU and pass a mask of flags? I think it wouldn't be difficult (or time consuming) for the scheduler to know that, but I am not 100% sure. IOW, the flags field in cpufreq_update_util() will represent all tasks in the rq, instead of just the task that is getting enqueued/dequeued.. And obviously we need to get some utilization numbers for the RT and DL tasks going forward, switching to max isn't going to work for ever :) -- viresh