Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753283AbdDLMP3 (ORCPT ); Wed, 12 Apr 2017 08:15:29 -0400 Received: from merlin.infradead.org ([205.233.59.134]:38072 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751218AbdDLMP1 (ORCPT ); Wed, 12 Apr 2017 08:15:27 -0400 Date: Wed, 12 Apr 2017 14:15:14 +0200 From: Peter Zijlstra To: Patrick Bellasi Cc: Tejun Heo , linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, Ingo Molnar , "Rafael J . Wysocki" , Paul Turner , Vincent Guittot , John Stultz , Todd Kjos , Tim Murray , Andres Oportus , Joel Fernandes , Juri Lelli , Chris Redpath , Morten Rasmussen , Dietmar Eggemann Subject: Re: [RFC v3 0/5] Add capacity capping support to the CPU controller Message-ID: <20170412121514.GE3093@worktop> References: <1488292722-19410-1-git-send-email-patrick.bellasi@arm.com> <20170320145131.GA3623@htj.duckdns.org> <20170320172233.GA28391@e110439-lin> <20170410073622.2y6tnpcd2ssuoztz@hirez.programming.kicks-ass.net> <20170411175833.GI29455@e110439-lin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170411175833.GI29455@e110439-lin> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 554 Lines: 13 On Tue, Apr 11, 2017 at 06:58:33PM +0100, Patrick Bellasi wrote: > We should consider also that at the CPUFreq side we already expose > knobs like scaling_{min,max}_freq which are much more platform > dependant than capacity. So I've always objected to these knobs. That said; they are a pre-existing user interface so changing them isn't really feasible much. But at the very least we should integrate them properly. Which for schedutil would mean they have to directly modify the relevant CPU capacity values. Is this currently done? (I think not.)