From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: defconfig: Select schedutil as default cpufreq governor
Date: Fri, 15 Dec 2017 15:50:41 +0000 [thread overview]
Message-ID: <20171215155040.mlvd56i2rfgd2e2t@armageddon.cambridge.arm.com> (raw)
In-Reply-To: <af12e002bc165844101830c0eb00e283b536a879.1510813288.git.viresh.kumar@linaro.org>
On Thu, Nov 16, 2017 at 11:51:36AM +0530, Viresh Kumar wrote:
> Currently performance governor is getting selected by default, which is
> surely not a very good choice as its pretty much power hungry.
>
> Select schedutil instead.
And why do we care about this in defconfig? People deploying their own
kernels in mobile may opt for this config, others may prefer the default
governor.
Also it seems it would be the only architecture make this governor the
default, so NAK.
--
Catalin
next prev parent reply other threads:[~2017-12-15 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 6:21 [PATCH] arm64: defconfig: Select schedutil as default cpufreq governor Viresh Kumar
2017-12-15 10:45 ` Viresh Kumar
2017-12-15 15:50 ` Catalin Marinas [this message]
2017-12-18 4:29 ` Viresh Kumar
2017-12-19 18:30 ` Marc Zyngier
2017-12-21 15:32 ` Arnd Bergmann
2017-12-22 4:46 ` Viresh Kumar
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=20171215155040.mlvd56i2rfgd2e2t@armageddon.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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