Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751693AbdG1DoH (ORCPT ); Thu, 27 Jul 2017 23:44:07 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:35852 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751595AbdG1DoF (ORCPT ); Thu, 27 Jul 2017 23:44:05 -0400 MIME-Version: 1.0 In-Reply-To: <20170727072146.uiuvadgsbpjk5gyb@e106622-lin> References: <20170727054635.GJ352@vireshk-i7> <20170727072146.uiuvadgsbpjk5gyb@e106622-lin> From: "Joel Fernandes (Google)" Date: Thu, 27 Jul 2017 20:44:03 -0700 Message-ID: Subject: Re: [Eas-dev] [PATCH V4 0/3] sched: cpufreq: Allow remote callbacks To: Juri Lelli Cc: Viresh Kumar , Joel Fernandes , eas-dev@lists.linaro.org, linux-pm@vger.kernel.org, Peter Zijlstra , Rafael Wysocki , Linux Kernel Mailing List , Ingo Molnar , Srinivas Pandruvada , Steve Muckle , Len Brown Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 862 Lines: 22 On Thu, Jul 27, 2017 at 12:21 AM, Juri Lelli wrote: [..] >> > >> > But even without that, if you see the routine >> > init_entity_runnable_average() in fair.c, the new tasks are >> > initialized in a way that they are seen as heavy tasks. And so even >> > for the first time they run, freq should normally increase on the >> > target CPU (at least with above application).i >> >> Ok, but the "heavy" in init_entity_runnable_average means for load, >> not the util_avg. The util_avg is what's used for frequency scaling >> IIUC and is set to 0 in that function no? >> > > True for init_entity_runnable_average(), but for new task post_init_ > entity_util_avg() is then also called (from wake_up_new_task()), which > modifies the initial util_avg value (depending on current rq {util, > load}_avg. Got it. That makes sense, thank you! -Joel