Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp7114626ybh; Thu, 8 Aug 2019 10:22:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqxo9mkI5zvNuIQrZR/Z7B6Q8Dt3oOQPpFCNql94HKEcUdCBU/qxronxrGv5SR4jpjdiWLRr X-Received: by 2002:a65:6497:: with SMTP id e23mr13191162pgv.89.1565284960267; Thu, 08 Aug 2019 10:22:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565284960; cv=none; d=google.com; s=arc-20160816; b=HbWqoPwuT/zWvAEeq6pPSnRNDVlcgLkUWK2pTA1LWTjFB1/pgG18C69RNfE6453nJb bHUIYjGS0rpy+doR1zPoHP4s/PhyPhIY0l+JX8sg5+VCl0ni8uRPjtIpaGcBkE3ktSUe HFy2Am/o0QUXYORp3mYzlmJQYn5OCkcz1HGNafudbHrQxsArCeBFnXjfgrfcOSfx55rg Ffz9ge+HdPTVAc6wT23H7KzsJQPeDczLLNvZob8RXhzuvyQhwiYad+KD4HcSRXB/QxxH 4lYr3rIhzVSFtXP0Ng2dwa8a1qLe6SG74BhJBNJ8HsYEBwKyxyGfWU2czdduqfC4O5sf dC6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=WIk8ZruA/Px2G9eGU0pZFO4NtTQXZo/aYyA9rKnU7Ss=; b=ZdTS6DkHqGaplOa9ewH7h89obn4JwqAjsoIOamjaJlA9jP7vTOT4fGqJ7x+O+HwuP2 mbK3RgWCABLusT7LoHq91Eg3xd19MeCtwx36wzcIZCYyApCHPzPVvrm1KIgqUcBYiQPJ YUYDtO3PdeYS6xIj3IpVu39u8EezC4kUjtPITzrYTf0las1c+BetmJFgEhN6cbjON2TC NylwO++K30hkyi07O3NZmIoCac6rGl+PkWr4WB9g7G4NzrOY10VbxZMsPdAAPeMVSI6t R69iQ+sA9NPgBwqM98sqGs4WqapAFmYc9n7hAsRx/2KRU1wt9MaacG8Rw55Jfx5vW+ky 4dkQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h16si48202755pgl.318.2019.08.08.10.22.19; Thu, 08 Aug 2019 10:22:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404270AbfHHRTw (ORCPT + 99 others); Thu, 8 Aug 2019 13:19:52 -0400 Received: from mx2.suse.de ([195.135.220.15]:54646 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2404098AbfHHRTw (ORCPT ); Thu, 8 Aug 2019 13:19:52 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 86A76AE48; Thu, 8 Aug 2019 17:19:50 +0000 (UTC) Date: Thu, 8 Aug 2019 19:19:49 +0200 From: Michal =?iso-8859-1?Q?Koutn=FD?= To: Patrick Bellasi Cc: Alessio Balsini , Dietmar Eggemann , Morten Rasmussen , Quentin Perret , Joel Fernandes , Paul Turner , Steve Muckle , Suren Baghdasaryan , Todd Kjos , Peter Zijlstra , "Rafael J . Wysocki" , Tejun Heo , VincentGuittot , Viresh Kumar , Juri Lelli , Ingo Molnar , cgroups@vger.kernel.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH v13 1/6] sched/core: uclamp: Extend CPU's cgroup controller Message-ID: <20190808171948.GF8617@blackbody.suse.cz> References: <20190802090853.4810-1-patrick.bellasi@arm.com> <20190802090853.4810-2-patrick.bellasi@arm.com> <20190806161133.GA18532@blackbody.suse.cz> <87imr74sfh.fsf@arm.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="w3uUfsyyY1Pqa/ej" Content-Disposition: inline In-Reply-To: <87imr74sfh.fsf@arm.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --w3uUfsyyY1Pqa/ej Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Aug 08, 2019 at 04:10:21PM +0100, Patrick Bellasi wrote: > Not sure to get what you mean here: I'm currently exposing uclamp to > both v1 and v2 hierarchies. cpu controller has different API for v1 and v2 hierarchies. My question reworded is -- are the new knobs exposed in the legacy API intentionally/for a reason? Michal --w3uUfsyyY1Pqa/ej Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEEoQaUCWq8F2Id1tNia1+riC5qSgFAl1MWbQACgkQia1+riC5 qSheLA/+K7nnjU6jLvL7D5MExUa3wdqwsunab8LGEYk4LMYktDs1F5j/xYnmae/Q iKPCSZhH+F4JDs3KlFhc4i7iroFAIdZXU7IArLa9vcTONhCYzt1EbmStW0QkjIQw 92w4FH3iPYIveSqDGwsU7zJsiwYHKjLQBSbeIrUM3ylvk0cfioap1WdZNS7/GEKR XcAgoyT2by2VArF0cxF38q1NCtre+Ash2T2r/3zM59arQb5OuR7uaXjloGeBAHox LQR539L9WsYPUx7qxNGeQxBPjzIbEHpApxmW2zwpV7It3qbiQaCOdf0KBjweaRri uIzCCq3PlwPqI+2klp57SNFEffrVYAS8MaBfz5eKD5MPIFw0r8/CO3pFSaGtZIUB Bbkl9ditoSPcaVYgcVuxgEwQbRanoS1jy6QTKoL2HGQ0ag3ThQYdxx7YQBsv3BV3 kjr988xDEi8dP15NEk83/eqrnUu5tbo2tOiN2THbhKlpFew6a/aYb7TIBzGUhKJN NouRmmvfp0fSo1lCsNuOjgp9rImU3jHgbhOUBavBPlt0GCGXk7CNtsuMCzjLw954 9kmjP0lSh4k8Nmm0vsODdmKbI6JPj8tAwM/LPCPBGgY+wKlAfD84Dgx6STN5tlmv uXyjHfelyL0velgb7yHnwVW7sxvN9/q52X9dwe5TbCzWwB4g5ak= =qSBD -----END PGP SIGNATURE----- --w3uUfsyyY1Pqa/ej--