From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751865AbdLSSsb (ORCPT ); Tue, 19 Dec 2017 13:48:31 -0500 Received: from bombadil.infradead.org ([65.50.211.133]:55805 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750798AbdLSSs0 (ORCPT ); Tue, 19 Dec 2017 13:48:26 -0500 Date: Tue, 19 Dec 2017 19:48:11 +0100 From: Peter Zijlstra To: Joel Fernandes Cc: linux-kernel@vger.kernel.org, Srinivas Pandruvada , Len Brown , "Rafael J. Wysocki" , Viresh Kumar , Ingo Molnar , Juri Lelli , Patrick Bellasi , Chris Redpath , Steve Muckle , Dietmar Eggemann , Vincent Guittot , Morten Ramussen , Frederic Weisbecker , Thomas Gleixner , Saravana Kannan , Vikram Mulukutla , Rohit Jain , Atish Patra , Josef Bacik , Rik van Riel , EAS Dev Subject: Re: [PATCH RESEND] cpufreq: schedutil: Use idle_calls counter of the remote CPU Message-ID: <20171219184811.campbfjw3plynurs@hirez.programming.kicks-ass.net> References: <20171219174712.13806-1-joelaf@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171219174712.13806-1-joelaf@google.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 19, 2017 at 09:47:12AM -0800, Joel Fernandes wrote: > Since the recent remote cpufreq callback work, its possible that a cpufreq > update is triggered from a remote CPU. For single policies however, the current > code uses the local CPU when trying to determine if the remote sg_cpu entered > idle or is busy. This is incorrect. To remedy this, compare with the nohz tick > idle_calls counter of the remote CPU. > > Acked-by: Viresh Kumar > Signed-off-by: Joel Fernandes Acked-by: Peter Zijlstra (Intel) > --- > Just resending this which is cpufreq-related as requested by Rafael rebased > on linus/master. > > The other 2 patches in my last series which can go in independent of this one are: > https://patchwork.kernel.org/patch/10115395/ > https://patchwork.kernel.org/patch/10115401/ > I'm still waiting on scheduler maintainers to comment on those. Unfortunately, > I haven't heard back anything yet since the last repost of those. Both of us have been somewhat preoccupied with that whole kaiser/pti thing the past few weeks. I have an absolutely stupid backlog :/