Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp412706ybi; Fri, 21 Jun 2019 01:43:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqwWuni5+6wrXoefAFzWzKw0B0135xsWC4GN2SHP/hoK7Gnonnaz4+aUzZ1nGXsKBHx4fcKd X-Received: by 2002:a17:902:1c9:: with SMTP id b67mr84302342plb.333.1561106623348; Fri, 21 Jun 2019 01:43:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561106623; cv=none; d=google.com; s=arc-20160816; b=gMYBP+Qo06LdOw7bE4rRyJ8rFKZOX/W3hArVvJaoXAbtCceqpB6gNkLsZjK079xE7/ LC/uM4WhSu4RqaUUT5OfxIh7Pmi+XQvynhOPwGVEP61rRTsyeWauY8blTf+26KNAeSO+ qYNcjtGEefZMvV6Erffh1bou33o8HkyKP6Q6aUNZMzBo6L6vC0QurlPNvIMjIyA1PIeE zwdDZ/qo5Z4B8kmSvl4lMGIQiyoiGO+fPMye+Fd7416vazfOcrYBfY/uh2AkZ2NGmWcG OCO6HOBtpvaE9/yA3+9bklbea6XX2AGyqWkCxlQff4YQCTQ/Nf9pWls1o0xiYBKtxhtw o7Lg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=VM0SuE/KaF3XRQzv9o69O6KRc+Rj/k2kbmUtS0xkiUQ=; b=NnKYHMBt3N4XLFGCob/SXtpx9UqumRLJ9GvmXiBG88/IyoVXuALN2JCggPr+HJMeTZ oxmEH9QECDVOPLrnQZmrCMo3Zd/e8Gqf1yy3mJ1TYrKjK6FasG5bM8CgzJUE87q4xF4J F4bsHWdaYUT2TASYqE+i9mwdYlS7vKy9p3yMIbnLD/a7v/c02g5s255nwk3Eq5XL7aQI BMpgfx1ssUxltINNaOB0EGELSdFW1ay5+pXSP36cC1ogi+5U2nDgDcpZPLKg/ZohtliH stAjwJ7966gt17Kjb9s4hF3YekohpoUGkoxps/DIEN/MERCzYD9omkL7hcvtpkSUgc9n 30IQ== 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 d37si2112272plb.351.2019.06.21.01.43.28; Fri, 21 Jun 2019 01:43:43 -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 S1726707AbfFUInD (ORCPT + 99 others); Fri, 21 Jun 2019 04:43:03 -0400 Received: from foss.arm.com ([217.140.110.172]:51018 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726657AbfFUInB (ORCPT ); Fri, 21 Jun 2019 04:43:01 -0400 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 B051A152D; Fri, 21 Jun 2019 01:43:00 -0700 (PDT) Received: from e110439-lin.cambridge.arm.com (e110439-lin.cambridge.arm.com [10.1.194.43]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 5D94F3F246; Fri, 21 Jun 2019 01:42:58 -0700 (PDT) From: Patrick Bellasi To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org Cc: Ingo Molnar , Peter Zijlstra , Tejun Heo , "Rafael J . Wysocki" , Vincent Guittot , Viresh Kumar , Paul Turner , Quentin Perret , Dietmar Eggemann , Morten Rasmussen , Juri Lelli , Todd Kjos , Joel Fernandes , Steve Muckle , Suren Baghdasaryan , Alessio Balsini Subject: [PATCH v10 10/16] sched/core: uclamp: Add uclamp_util_with() Date: Fri, 21 Jun 2019 09:42:11 +0100 Message-Id: <20190621084217.8167-11-patrick.bellasi@arm.com> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190621084217.8167-1-patrick.bellasi@arm.com> References: <20190621084217.8167-1-patrick.bellasi@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org So far uclamp_util() allows to clamp a specified utilization considering the clamp values requested by RUNNABLE tasks in a CPU. For the Energy Aware Scheduler (EAS) it is interesting to test how clamp values will change when a task is becoming RUNNABLE on a given CPU. For example, EAS is interested in comparing the energy impact of different scheduling decisions and the clamp values can play a role on that. Add uclamp_util_with() which allows to clamp a given utilization by considering the possible impact on CPU clamp values of a specified task. Signed-off-by: Patrick Bellasi Cc: Ingo Molnar Cc: Peter Zijlstra --- kernel/sched/core.c | 13 +++++++++++++ kernel/sched/sched.h | 21 ++++++++++++++++++++- 2 files changed, 33 insertions(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index ab75e874fdcc..2226ddd1de04 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -869,6 +869,19 @@ uclamp_eff_get(struct task_struct *p, unsigned int clamp_id) return uc_req; } +unsigned int uclamp_eff_value(struct task_struct *p, unsigned int clamp_id) +{ + struct uclamp_se uc_eff; + + /* Task currently refcounted: use back-annotated (effective) value */ + if (p->uclamp[clamp_id].active) + return p->uclamp[clamp_id].value; + + uc_eff = uclamp_eff_get(p, clamp_id); + + return uc_eff.value; +} + /* * When a task is enqueued on a rq, the clamp bucket currently defined by the * task's uclamp::bucket_id is refcounted on that rq. This also immediately diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h index c33a57f14743..ce2da8b9ff8c 100644 --- a/kernel/sched/sched.h +++ b/kernel/sched/sched.h @@ -2266,11 +2266,20 @@ static inline void cpufreq_update_util(struct rq *rq, unsigned int flags) {} #endif /* CONFIG_CPU_FREQ */ #ifdef CONFIG_UCLAMP_TASK -static inline unsigned int uclamp_util(struct rq *rq, unsigned int util) +unsigned int uclamp_eff_value(struct task_struct *p, unsigned int clamp_id); + +static __always_inline +unsigned int uclamp_util_with(struct rq *rq, unsigned int util, + struct task_struct *p) { unsigned int min_util = READ_ONCE(rq->uclamp[UCLAMP_MIN].value); unsigned int max_util = READ_ONCE(rq->uclamp[UCLAMP_MAX].value); + if (p) { + min_util = max(min_util, uclamp_eff_value(p, UCLAMP_MIN)); + max_util = max(max_util, uclamp_eff_value(p, UCLAMP_MAX)); + } + /* * Since CPU's {min,max}_util clamps are MAX aggregated considering * RUNNABLE tasks with _different_ clamps, we can end up with an @@ -2281,7 +2290,17 @@ static inline unsigned int uclamp_util(struct rq *rq, unsigned int util) return clamp(util, min_util, max_util); } + +static inline unsigned int uclamp_util(struct rq *rq, unsigned int util) +{ + return uclamp_util_with(rq, util, NULL); +} #else /* CONFIG_UCLAMP_TASK */ +static inline unsigned int uclamp_util_with(struct rq *rq, unsigned int util, + struct task_struct *p) +{ + return util; +} static inline unsigned int uclamp_util(struct rq *rq, unsigned int util) { return util; -- 2.21.0