Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp466077pxb; Thu, 12 Nov 2020 08:07:05 -0800 (PST) X-Google-Smtp-Source: ABdhPJw2N+9oF08vj4UkEgi4ddB9EHIBWeFWiyMGD5cBUMSvj/qjNefxlo/GCgI9HnkswTlSnhCG X-Received: by 2002:adf:c14c:: with SMTP id w12mr334474wre.40.1605197224962; Thu, 12 Nov 2020 08:07:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605197224; cv=none; d=google.com; s=arc-20160816; b=cWYkpvA+iTcdekdBy4tcgFkF0OO+G5iSAd/8ug6nFcoo1OD7oSX5vfF29TKgXhRyX1 BBtXIGoVopg94hUJrdzfDBN9nbNePJENCdIGKYCImKNw8tq4xGt6A7lcXD2VvP2QddBg 54mdldwq6MrYZRVCI35usv6puh7lumgwjrPCyMp+lnyS30he37Grdze4rt58ATRvWCR+ vOJu6RapMuXao6PuKHYSR3jEa+tDHtGli33wOFJVorOuEMI4iTy3UsvfAVjjFuYUf6xB ZnzXa7D3a30wt9WsSUlPvnpbGISPge8t2KxEKDFSc+SKHUTZnY8CbOUA2pIjm2B4tDaY HDqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=UsUhHC6paD3gUqNbB+k3ro8Dl4BawzY3By/iZhD65k0=; b=D1J7eDDrCcCPd7Ui6QfgkFPjGDHZ++Z/EyicoRm2udXOaCC+j+wF1LsJHXYPklBWmS CwDfy0UoKhzFHRO6CS4PT3WgkV/1hi97zxrQ5m7WhISkuhYJAxu5AukSlqkmzkEiULgZ WMQQg0QdospGB0Qdk/9MiFQyzuxxjoddTMvH30mPaFinxJB4gz5QrSjq9HIiBnvkHP20 toQImYU7laGk5ImmrxYeYGpCuva5/z+DOESMmz6GUnCWikCy2KL7jhsCZy0VGw1rGYFV 8kpD8mBnSZufN7ucPixulPpTqnV82z8VctgwYrkTZgmbsP8+I8Zb13eia07q7DKgmaWg g5Cw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cb12si3876418edb.272.2020.11.12.08.06.39; Thu, 12 Nov 2020 08:07:04 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728683AbgKLQBu (ORCPT + 99 others); Thu, 12 Nov 2020 11:01:50 -0500 Received: from foss.arm.com ([217.140.110.172]:53392 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728430AbgKLQBt (ORCPT ); Thu, 12 Nov 2020 11:01:49 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5CDBF142F; Thu, 12 Nov 2020 08:01:49 -0800 (PST) Received: from [192.168.178.2] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C1F843F73C; Thu, 12 Nov 2020 08:01:47 -0800 (PST) Subject: Re: [PATCH v5 1/1] sched/uclamp: add SCHED_FLAG_UTIL_CLAMP_RESET flag to reset uclamp To: Qais Yousef Cc: Peter Zijlstra , Yun Hsiang , linux-kernel@vger.kernel.org, patrick.bellasi@matbug.net, kernel test robot References: <20201103023756.1012088-1-hsiang023167@gmail.com> <20201110122108.GG2594@hirez.programming.kicks-ass.net> <20201112144131.7gqglj435bs6otwm@e107158-lin.cambridge.arm.com> From: Dietmar Eggemann Message-ID: Date: Thu, 12 Nov 2020 17:01:46 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20201112144131.7gqglj435bs6otwm@e107158-lin.cambridge.arm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/11/2020 15:41, Qais Yousef wrote: > On 11/11/20 18:41, Dietmar Eggemann wrote: >> On 10/11/2020 13:21, Peter Zijlstra wrote: >>> On Tue, Nov 03, 2020 at 10:37:56AM +0800, Yun Hsiang wrote: [...] > I assume we agree then that we don't want to explicitly document this quirky > feature and keep it for advanced users? > > I am wary of the UAPI change that is both explicit and implicit. It explicitly > requests a reset, but implicitly requests a cgroup behavior change. > > With this magic value at least we can more easily return an error if we decided > to deprecate it, which has been my main ask so far. I don't want us to end up > not being able to easily modify this code in the future. Another advantage for this 'magic value' approach. > I don't have strong opinion too though. > > If you or Yun would still like to send the patch to protect > SCHED_FLAG_UTIL_CLAMP and SCHED_FLAG_ALL with __kernel__ that'd be great. Ah yes! Can add an extra patch for this when sending out the next version. [...]