From: Quentin Perret <qperret@google.com>
To: Doug Smythies <dsmythies@telus.net>
Cc: juri.lelli@redhat.com, kernel-team@android.com,
vincent.guittot@linaro.org, arnd@arndb.de,
linux-pm@vger.kernel.org, peterz@infradead.org,
adharmap@codeaurora.org, rafael@kernel.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, viresh.kumar@linaro.org,
mingo@redhat.com, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org, tkjos@google.com
Subject: Re: [PATCH v2 0/2] cpufreq: Specify the default governor on command line
Date: Tue, 23 Jun 2020 19:04:37 +0100 [thread overview]
Message-ID: <20200623180437.GA248517@google.com> (raw)
In-Reply-To: <002201d64987$5dc93b90$195bb2b0$@net>
Hi Doug,
On Tuesday 23 Jun 2020 at 10:54:33 (-0700), Doug Smythies wrote:
> Hi Quentin,
>
> Because I am lazy and sometimes do not want to recompile
> the distro source, I have a need/desire for this.
Good to know I'm not the only one ;-)
> Tested these two grub command lines:
>
> GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 consoleblank=300 intel_pstate=disable cpufreq.default_governor=schedutil cpuidle_sysfs_switch cpuidle.governor=teo"
>
> And
>
> #GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 consoleblank=450 intel_pstate=passive cpufreq.default_governor=schedutil cpuidle_sysfs_switch cpuidle.governor=teo"
>
> And all worked as expected. I use Ubuntu as my distro, and also had to disable a startup script that switches to "ondemand", or similar, after 1 minute.
Good, thanks for giving it a try.
> As a side note (separate subject, but is one reason I tried it):
> My i5-9600K based computer seems to hit a power limit during boot approximately 3 seconds after kernel selection on grub.
> This had no effect on that issue (even when selecting powersave governor).
Interesting ... Could you confirm that compiling with powersave as
default doesn't fix the issue either?
Other question, when does the intel_pstate driver start on your device?
Before or after that 3 seconds boot time?
Thanks,
Quentin
next prev parent reply other threads:[~2020-06-23 18:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 14:21 [PATCH v2 0/2] cpufreq: Specify the default governor on command line Quentin Perret
2020-06-23 14:21 ` [PATCH v2 1/2] cpufreq: Register governors at core_initcall Quentin Perret
2020-06-23 14:21 ` [PATCH v2 2/2] cpufreq: Specify default governor on command line Quentin Perret
2020-06-24 5:50 ` Viresh Kumar
2020-06-24 12:51 ` Rafael J. Wysocki
2020-06-24 15:32 ` Quentin Perret
2020-06-25 8:50 ` Viresh Kumar
2020-06-25 10:52 ` Rafael J. Wysocki
2020-06-25 11:36 ` Viresh Kumar
2020-06-25 11:44 ` Rafael J. Wysocki
2020-06-25 11:53 ` Quentin Perret
2020-06-25 13:28 ` Rafael J. Wysocki
2020-06-25 13:49 ` Quentin Perret
2020-06-25 14:08 ` Rafael J. Wysocki
2020-06-26 2:53 ` Viresh Kumar
2020-06-26 8:09 ` Quentin Perret
2020-06-23 17:54 ` [PATCH v2 0/2] cpufreq: Specify the " Doug Smythies
2020-06-23 18:04 ` Quentin Perret [this message]
2020-06-24 0:07 ` Doug Smythies
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=20200623180437.GA248517@google.com \
--to=qperret@google.com \
--cc=adharmap@codeaurora.org \
--cc=arnd@arndb.de \
--cc=dsmythies@telus.net \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tkjos@google.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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;
as well as URLs for NNTP newsgroup(s).