Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp3680337pxv; Mon, 5 Jul 2021 03:14:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwwrOxZ6DYOnK3ilRd71wg8i3i07pffcTO96y/Ji9wqvAK9PKtB2tEgL5odfi27ho4E83fk X-Received: by 2002:a17:907:9602:: with SMTP id gb2mr9211139ejc.119.1625480044281; Mon, 05 Jul 2021 03:14:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625480044; cv=none; d=google.com; s=arc-20160816; b=1D4GBAE1/7xFh+oAMy6Am9PC3nkNwP9+kTRbFKOZhiwf1R146hLmZRPkLHQaehnR+l qq8nyCWLnBqA62y0TG/XgftcmE/Mv4ghZ7Y+pGbWLwbxsZb1HXqmaMHrlZPPxg0M8hXr d1y+tEw3tPBb1oqMnFw+oDXoKgmKVQICXmcI5SXh32C8uOgpKYYoNE7RG5+hxngZbLRV hbeGHI2AzNFWXsMwZ8n5QzlQg1l98cZIoZLgT2g1tQVS1Tpbt3yPNiciXLWAuh2GOCOI aeo9TyLryIqIlGgRfOmsFrHjpzyzj+fa9AEHPViWaz6vybOgGvaCy3YAp8oLhaxb812Q pa1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=2AEYIcLi6JoP4L9reiM7rLqpk8JyNvT0xJKnxWnbcP0=; b=cIgqyRYUEAd3l7pRvhS1mrMiv5Aq0yLMPm1gEzkjpLc4MFyR6CbYd1L8NgQu9xwV1j Sdnot2dRdrNaz8milA0tW8ZFeP7UU6N7/Oc0RTitdQI9+E18MK2kHL/WEJI7zwQbKiT1 6l/AFzqtpnlDhTfEBqihheyULOxzXiLu6gWQfMwrA4LwcHoTGl8EPq5U9TsWQ/j5ZpPx GCtSNhFrRRo1u+Okm6zXNL32OhVMYV+vdlHM477nJWnflWrwtyq9524kgM9wjaLXvQSg aiUdBM1OggSoyzyNgMXDYDoXBuudVn6sUFNzTHzvFSu13N0voq/TMXvLSVKdFlyZVKui vlEQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=NYqY9lR5; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bf3si11104688edb.23.2021.07.05.03.13.40; Mon, 05 Jul 2021 03:14:04 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=NYqY9lR5; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230458AbhGEKPV (ORCPT + 99 others); Mon, 5 Jul 2021 06:15:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:39540 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230366AbhGEKPV (ORCPT ); Mon, 5 Jul 2021 06:15:21 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 385D3613F3; Mon, 5 Jul 2021 10:12:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1625479964; bh=9zmE0VZ4KzHVsemp5Tdz858sT5sH/HJRKbZtTp3SHKY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=NYqY9lR5lKVot9XCsbnbUtJCyIwHVl15RHe4sTktbHXVnfonEeXGbOVJ9aojl6uS1 h8eqImiRy0ujk/4FG1aJ+Ozz4r00RNNT8RxzUhaSHA9cDBaGDh9viZ+kBHmo5ZzFI4 +Vzfa7fmn4ynfthYx+5intEXJVpGhl3Qzt+o3vNleOvzeODGLA8qHIbT7rsdjK/tMA T4SuLNHg+g5eb7Moi2rBCqmtOK3sdp6ba5WEwTCJpjJPsJNLwgxWYRdsBMBJBa2Iau U/FDfpeuQAyq55gu6GAxMXdeoirpv977to/gXU0kqPhT86popiROHm126/pNWaIuUn N+SLCdeikhKsQ== Date: Mon, 5 Jul 2021 06:12:43 -0400 From: Sasha Levin To: Lukasz Luba Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org, Peter Zijlstra , Vincent Guittot , Dietmar Eggemann , Greg KH Subject: Re: [PATCH AUTOSEL 5.12 62/80] sched/fair: Take thermal pressure into account while estimating energy Message-ID: References: <20210704230616.1489200-1-sashal@kernel.org> <20210704230616.1489200-62-sashal@kernel.org> <54648043-4944-08f9-8ce8-8413d8037450@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <54648043-4944-08f9-8ce8-8413d8037450@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 05, 2021 at 09:13:59AM +0100, Lukasz Luba wrote: >Hi Sasha, > >+CC Greg > >On 7/5/21 12:05 AM, Sasha Levin wrote: >>From: Lukasz Luba >> >>[ Upstream commit 489f16459e0008c7a5c4c5af34bd80898aa82c2d ] >> >>Energy Aware Scheduling (EAS) needs to be able to predict the frequency >>requests made by the SchedUtil governor to properly estimate energy used >>in the future. It has to take into account CPUs utilization and forecast >>Performance Domain (PD) frequency. There is a corner case when the max >>allowed frequency might be reduced due to thermal. SchedUtil is aware of >>that reduced frequency, so it should be taken into account also in EAS >>estimations. >> >>SchedUtil, as a CPUFreq governor, knows the maximum allowed frequency of >>a CPU, thanks to cpufreq_driver_resolve_freq() and internal clamping >>to 'policy::max'. SchedUtil is responsible to respect that upper limit >>while setting the frequency through CPUFreq drivers. This effective >>frequency is stored internally in 'sugov_policy::next_freq' and EAS has >>to predict that value. >> >>In the existing code the raw value of arch_scale_cpu_capacity() is used >>for clamping the returned CPU utilization from effective_cpu_util(). >>This patch fixes issue with too big single CPU utilization, by introducing >>clamping to the allowed CPU capacity. The allowed CPU capacity is a CPU >>capacity reduced by thermal pressure raw value. >> >>Thanks to knowledge about allowed CPU capacity, we don't get too big value >>for a single CPU utilization, which is then added to the util sum. The >>util sum is used as a source of information for estimating whole PD energy. >>To avoid wrong energy estimation in EAS (due to capped frequency), make >>sure that the calculation of util sum is aware of allowed CPU capacity. >> >>This thermal pressure might be visible in scenarios where the CPUs are not >>heavily loaded, but some other component (like GPU) drastically reduced >>available power budget and increased the SoC temperature. Thus, we still >>use EAS for task placement and CPUs are not over-utilized. >> >>Signed-off-by: Lukasz Luba >>Signed-off-by: Peter Zijlstra (Intel) >>Reviewed-by: Vincent Guittot >>Reviewed-by: Dietmar Eggemann >>Link: https://lore.kernel.org/r/20210614191128.22735-1-lukasz.luba@arm.com >>Signed-off-by: Sasha Levin >>--- >> kernel/sched/fair.c | 11 ++++++++--- >> 1 file changed, 8 insertions(+), 3 deletions(-) > >It has been picked up automatically right? >To make it fully working you need also this patch: >https://lore.kernel.org/linux-pm/20210614191030.22241-1-lukasz.luba@arm.com/ > >It makes sure that the thermal pressure signal gets proper >information also for CPUs which were offline and then wake-up. >It has a proper fix tagging with commit hash id. >That patch can be ported to stable: v5.6+ >I can send it to stable list. Please let me know if you need >any help. > >The same applies to patch which I found for v5.13-stable: >[PATCH AUTOSEL 5.13 65/85] sched/fair: Take thermal pressure into >account while estimating energy >https://lore.kernel.org/stable/20210704230420.1488358-65-sashal@kernel.org/T/#u I took that patch for 5.13-5.10, thanks! -- Thanks, Sasha