From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: Thara Gopinath <thara.gopinath@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: v5.7: new core kernel option missing help text
Date: Wed, 3 Jun 2020 19:45:00 +0100 [thread overview]
Message-ID: <20200603184500.GC1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <jhjh7vshvwl.mognet@arm.com>
On Wed, Jun 03, 2020 at 07:00:26PM +0100, Valentin Schneider wrote:
>
> On 03/06/20 18:31, Russell King - ARM Linux admin wrote:
> > Hi,
> >
> > A new kernel configuration option ("SCHED_THERMAL_PRESSURE") was
> > recently added, but has no help text. This is most unhelpful when
> > trying to configure the kernel, since one does not know what the
> > effect of answering yes or no to this option would be.
> >
> > Please supply a proper help text when adding core kernel options
> > so that people can make an informed decision when answering the
> > prompt, rather than just guessing.
> >
>
> Right; does the below look good enough?
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.
>
> ---
> diff --git a/init/Kconfig b/init/Kconfig
> index 74a5ac65644f..f40cf852d00a 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -441,6 +441,10 @@ config HAVE_SCHED_AVG_IRQ
> config SCHED_THERMAL_PRESSURE
> bool "Enable periodic averaging of thermal pressure"
> depends on SMP
> + help
> + This option allows the scheduler to be aware of CPU thermal throttling
> + (i.e. thermal pressure), providing arch_scale_thermal_pressure() is
> + implemented.
>
> config BSD_PROCESS_ACCT
> bool "BSD Process Accounting"
> ---
>
--
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
next prev parent reply other threads:[~2020-06-03 18:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 17:31 Russell King - ARM Linux admin
2020-06-03 18:00 ` Valentin Schneider
2020-06-03 18:45 ` Russell King - ARM Linux admin [this message]
2020-06-03 19:24 ` Vincent Guittot
2020-06-03 19:58 ` Russell King - ARM Linux admin
2020-06-03 20:22 ` Vincent Guittot
2020-06-03 20:25 ` Valentin Schneider
2020-06-04 0:48 ` Thara Gopinath
2020-06-04 9:26 ` Valentin Schneider
2020-06-04 9:29 ` Russell King - ARM Linux admin
2020-06-04 10:56 ` Valentin Schneider
[not found] ` <CALD-y_zQms4YQup2MgAfNhWSu=ewkhossHma2TKqfTcOFaG=uA@mail.gmail.com>
2020-06-04 15:38 ` Valentin Schneider
2020-06-04 22:22 ` Thara Gopinath
2020-06-05 7:03 ` Vincent Guittot
2020-06-05 9:46 ` Valentin Schneider
2020-06-05 8:15 ` Russell King - ARM Linux admin
2020-06-05 10:02 ` Valentin Schneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200603184500.GC1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=thara.gopinath@linaro.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome