From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753386AbcBJTrM (ORCPT ); Wed, 10 Feb 2016 14:47:12 -0500 Received: from mail-pf0-f181.google.com ([209.85.192.181]:35285 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752695AbcBJTrK (ORCPT ); Wed, 10 Feb 2016 14:47:10 -0500 Subject: Re: [PATCH 0/3] cpufreq: Replace timers with utilization update callbacks To: "Rafael J. Wysocki" References: <3071836.JbNxX8hU6x@vostro.rjw.lan> <56B93548.9090006@linaro.org> <5387313.xAhVpzgZCg@vostro.rjw.lan> <56BA8C29.4090905@linaro.org> Cc: "Rafael J. Wysocki" , Peter Zijlstra , Linux PM list , Linux Kernel Mailing List , Srinivas Pandruvada , Viresh Kumar , Juri Lelli , Thomas Gleixner From: Steve Muckle X-Enigmail-Draft-Status: N1110 Message-ID: <56BB93BB.5050405@linaro.org> Date: Wed, 10 Feb 2016 11:47:07 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/09/2016 07:09 PM, Rafael J. Wysocki wrote: >>> >> I think additional hooks such as enqueue/dequeue would be needed in >>> >> RT/DL. The task tick callbacks will only run if a task in that class is >>> >> executing at the time of the tick. There could be intermittent RT/DL >>> >> task activity in a frequency domain (the only task activity there, no >>> >> CFS tasks) that doesn't happen to overlap the tick. Worst case the task >>> >> activity could be periodic in such a way that it never overlaps the tick >>> >> and the update is never made. >> > >> > So if I'm reading this correctly, it would be better to put the hooks >> > into update_curr_rt/dl()? That should AFAICS be sufficient to avoid stalling. It may be more than is required as that covers more than just enqueue/dequeue but I'm not sure offhand. > > If done this way, I guess we may pass rq_clock_task(rq) as the time > arg to cpufreq_update_util() from there and then the cpu_lock() call > I've added to this prototype won't be necessary any more. Is it rq_clock_task() or rq_clock()? The former can omit irq time so may gradually fall behind wall clock time, delaying callbacks in cpufreq. thanks, Steve