Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DEF00C6379F for ; Tue, 21 Feb 2023 12:21:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234565AbjBUMVj (ORCPT ); Tue, 21 Feb 2023 07:21:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42988 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234009AbjBUMVg (ORCPT ); Tue, 21 Feb 2023 07:21:36 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 9EC5F29E3C for ; Tue, 21 Feb 2023 04:21:11 -0800 (PST) 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 71695FEC; Tue, 21 Feb 2023 04:11:27 -0800 (PST) Received: from [10.57.14.135] (unknown [10.57.14.135]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B1F263F703; Tue, 21 Feb 2023 04:10:42 -0800 (PST) Message-ID: Date: Tue, 21 Feb 2023 12:10:41 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH v2 3/3] sched/tp: Add new tracepoint to track compute energy computation Content-Language: en-US To: Qais Yousef Cc: linux-kernel@vger.kernel.org, Wei Wang , Vincent Guittot , Xuewen Yan , Hank , Jonathan JMChen , Ingo Molnar , Peter Zijlstra , Dietmar Eggemann References: <20230205224318.2035646-1-qyousef@layalina.io> <20230205224318.2035646-4-qyousef@layalina.io> <20230221120832.x642tqohxv5nascr@airbuntu> From: Lukasz Luba In-Reply-To: <20230221120832.x642tqohxv5nascr@airbuntu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/21/23 12:08, Qais Yousef wrote: > On 02/20/23 11:22, Lukasz Luba wrote: >> Hi Qais, >> >> On 2/5/23 22:43, Qais Yousef wrote: >>> It was useful to track feec() placement decision and debug the spare >>> capacity and optimization issues vs uclamp_max. >>> >>> Signed-off-by: Qais Yousef >>> --- >>> include/trace/events/sched.h | 4 ++++ >>> kernel/sched/core.c | 1 + >>> kernel/sched/fair.c | 7 ++++++- >>> 3 files changed, 11 insertions(+), 1 deletion(-) >>> >>> diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h >>> index fbb99a61f714..20cc884f72ff 100644 >>> --- a/include/trace/events/sched.h >>> +++ b/include/trace/events/sched.h >>> @@ -735,6 +735,10 @@ DECLARE_TRACE(sched_update_nr_running_tp, >>> TP_PROTO(struct rq *rq, int change), >>> TP_ARGS(rq, change)); >>> +DECLARE_TRACE(sched_compute_energy_tp, >>> + TP_PROTO(struct task_struct *p, int dst_cpu, unsigned long energy), >>> + TP_ARGS(p, dst_cpu, energy)); >>> + >>> #endif /* _TRACE_SCHED_H */ >>> /* This part must be outside protection */ >>> diff --git a/kernel/sched/core.c b/kernel/sched/core.c >>> index 4580fe3e1d0c..5f6dde9b892b 100644 >>> --- a/kernel/sched/core.c >>> +++ b/kernel/sched/core.c >>> @@ -110,6 +110,7 @@ EXPORT_TRACEPOINT_SYMBOL_GPL(sched_overutilized_tp); >>> EXPORT_TRACEPOINT_SYMBOL_GPL(sched_util_est_cfs_tp); >>> EXPORT_TRACEPOINT_SYMBOL_GPL(sched_util_est_se_tp); >>> EXPORT_TRACEPOINT_SYMBOL_GPL(sched_update_nr_running_tp); >>> +EXPORT_TRACEPOINT_SYMBOL_GPL(sched_compute_energy_tp); >>> DEFINE_PER_CPU_SHARED_ALIGNED(struct rq, runqueues); >>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c >>> index a8c3d92ff3f6..801e903c4307 100644 >>> --- a/kernel/sched/fair.c >>> +++ b/kernel/sched/fair.c >>> @@ -7295,11 +7295,16 @@ compute_energy(struct energy_env *eenv, struct perf_domain *pd, >>> { >>> unsigned long max_util = eenv_pd_max_util(eenv, pd_cpus, p, dst_cpu); >>> unsigned long busy_time = eenv->pd_busy_time; >>> + unsigned long energy; >>> if (dst_cpu >= 0) >>> busy_time = min(eenv->pd_cap, busy_time + eenv->task_busy_time); >>> - return em_cpu_energy(pd->em_pd, max_util, busy_time, eenv->cpu_cap); >>> + energy = em_cpu_energy(pd->em_pd, max_util, busy_time, eenv->cpu_cap); >>> + >>> + trace_sched_compute_energy_tp(p, dst_cpu, energy); >> >> Could we also dump the max_util and busy_time? > > We certainly can :) Great, thanks!