Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp763684ybg; Wed, 3 Jun 2020 13:01:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyaYVsFzFiK96oOihWWrgVivwyMmNORS4VepEPESE0b/S7wOOgcKOj2pWzVB4Kjy/CD+m+U X-Received: by 2002:a17:906:7a19:: with SMTP id d25mr866499ejo.333.1591214489847; Wed, 03 Jun 2020 13:01:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591214489; cv=none; d=google.com; s=arc-20160816; b=NELHhy9elaz/eWc0cV0lFBXxD8fG1vVyTiMEQfwv024IkjFail/g2exiFqF7nzCDYm gXGE0rbrHB0ePWw6tiiklJEsxW5rlfuTQlW6zbo4iBXykLJb0m5THv9+ieAHqm9tZfJb aK8/3AK9rKYXBpKR34BlbnP8ZAkOmqGAMnBQK1/y/GVpN8kSPPX/5yuGqewoiTK9IkYp 7uuiby0LDHye0PYRFetE1pOBuk+qulWAlv+l1pBcaNdaYepAMs7A1FDRNPepSDTml4zl c083tDJG/lh77i6IJ3ETTD2s2pYIYPefJtt69Ay/4KANX5rsMw8j3RM3gYlDBdj3f00l 6/cQ== 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:dkim-signature; bh=tg8mNhsE0qlps5ciALLkNONY+9bvqdzo03558zZho/4=; b=MsqpHPGXK/dSh3zu43nN4DFfRSwPwxsFhMIeIUtHQeceODmmoc4r07s25uAPk5oURo qxyl/DRpYLl0WFbhd3Ek64yRKn/6PYEiPZPM2rYQToxiPIM8hHNBORlhZU8DB96gLwk9 ugwpDTPdPMOPit4gh5HboqIU8pF/3VOniJxnAqye6p1C/BN0DOsoFUwCQyWM8eNnh9NJ a8FU8YgQZMcDq3hndSnpewAFvPVyQ/ccGJoGs9+MeIQd8sngPHuQe/HNFsPW2OgjM/E7 SuiGYRW7jA0pnfPm0h+5eCrJJWuIWJsJmRzlBaEq0wLmaPnjU1yvvOYu7x9H+RFWvI8W STDw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@armlinux.org.uk header.s=pandora-2019 header.b="Wh/2nlbR"; 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=armlinux.org.uk Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 36si305698edp.290.2020.06.03.13.01.03; Wed, 03 Jun 2020 13:01:29 -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=fail (test mode) header.i=@armlinux.org.uk header.s=pandora-2019 header.b="Wh/2nlbR"; 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=armlinux.org.uk Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725992AbgFCT7E (ORCPT + 99 others); Wed, 3 Jun 2020 15:59:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51026 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725922AbgFCT7E (ORCPT ); Wed, 3 Jun 2020 15:59:04 -0400 Received: from pandora.armlinux.org.uk (pandora.armlinux.org.uk [IPv6:2001:4d48:ad52:3201:214:fdff:fe10:1be6]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AFDABC08C5C0 for ; Wed, 3 Jun 2020 12:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=tg8mNhsE0qlps5ciALLkNONY+9bvqdzo03558zZho/4=; b=Wh/2nlbRDwoeC9J0ac3xyk/Jk zQty8vNNDayaTgr5QL1Xvauoyc93BcKurh2nK51uQqfprOqyUVUfoXXIOgnlFizlapzncHwENxKAp 48NUwyvSWDRNdpi/K/7btTTyXaEmO/CVluzeLa1uYicu0Qg/S7tJqOevW0d+S3jky8khAgqAhAARe It3hNKj7C5OahkvOvhB1SXbhV6dqZZyM4KeKmXAbIbIh0Bb4S0gNeY27dUSvqw8TNp6WmhMtXPEKD 2u7VQX77SBjmniwTjflfdwgnLUhW5/aw+JmNV4kp6QNUC3RtgrK73RAM/lOSnJ+DceYynFWPNj1zB dOiWsf49A==; Received: from shell.armlinux.org.uk ([2001:4d48:ad52:3201:5054:ff:fe00:4ec]:48984) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jgZXM-0006E7-IL; Wed, 03 Jun 2020 20:58:56 +0100 Received: from linux by shell.armlinux.org.uk with local (Exim 4.92) (envelope-from ) id 1jgZXJ-0005fr-Uq; Wed, 03 Jun 2020 20:58:53 +0100 Date: Wed, 3 Jun 2020 20:58:53 +0100 From: Russell King - ARM Linux admin To: Vincent Guittot Cc: Valentin Schneider , Thara Gopinath , linux-kernel Subject: Re: v5.7: new core kernel option missing help text Message-ID: <20200603195853.GD1551@shell.armlinux.org.uk> References: <20200603173150.GB1551@shell.armlinux.org.uk> <20200603184500.GC1551@shell.armlinux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 On Wed, Jun 03, 2020 at 09:24:56PM +0200, Vincent Guittot wrote: > On Wed, 3 Jun 2020 at 20:45, Russell King - ARM Linux admin > wrote: > > It's a start. I'm still wondering whether I should answer yes or no > > for the platforms I'm building for. > > > > So far, all I've found is: > > > > arch/arm/include/asm/topology.h:#define arch_scale_thermal_pressure topology_get_thermal_pressure > > > > which really doesn't tell me anything about this. So I'm still in > > the dark. > > > > I guess topology_get_thermal_pressure is provided by something in > > drivers/ which will be conditional on some driver or something. > > You need cpufreq_cooling device to make it useful and only for SMP > I don't think that this should not be user configurable because even > with the description above, it is not easy to choose. > This should be set by the driver that implement the feature which is > only cpufreq cooling device for now it As I have CONFIG_CPU_FREQ_THERMAL=y in my config, I'm guessing (and it's only a guess) that I should say y to SCHED_THERMAL_PRESSURE ? > > > + help > > > + This option allows the scheduler to be aware of CPU thermal throttling > > > + (i.e. thermal pressure), providing arch_scale_thermal_pressure() is > > > + implemented. Is this feature documented in terms of what it does? Do I assume that as the thermal trip points start tripping, that has an influence on the scheduler? Or is it the case that the scheduler is wanting to know when the cpu frequency changes? Grepping for "thermal" in Documentation/scheduler brings up nothing. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up