From: "Doug Smythies" <dsmythies@telus.net>
To: 'Stratos Karafotis' <stratosk@semaphore.gr>
Cc: "'Rafael J. Wysocki'" <rafael@kernel.org>,
"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
'Linux PM' <linux-pm@vger.kernel.org>,
'Andy Tang' <andy.tang@nxp.com>,
'Viresh Kumar' <viresh.kumar@linaro.org>
Subject: RE: Ask for help on governor
Date: Thu, 14 Dec 2017 17:29:50 -0800 [thread overview]
Message-ID: <001e01d37544$354e82c0$9feb8840$@net> (raw)
In-Reply-To: PYBveIvmB7WlePYC0enKU6
Hi,
On 2017.12.14 Stratos Karafotis wrote:
> I'm not sure I understood what the problem is (maybe because I can't see
> the description of the issue in the quotes).
For my part of it, the problem is that the default sample_period for
the intel_cpufreq scaling driver (i.e. intel_pstate in passive mode)
is 500 uSec. Everything, as far as I can determine, becomes busted if
the sampling period is less than a jiffy.
By the way, the default sampling period for the acpi_cpufreq driver seems to be
10 milliseconds, and everything is fine. I do not know why the defaults for
the intel_cpufreq driver are so short, and suggest that they shouldn't be,
in which case your commit might be O.K.
>
> Commit 00bfe05889e91b5112893b001e4a47b0a0f8bdd7 affects only conservative
> governor.
> Do you have the same issue with ondemand too?
Yes, this entire thread has been about the conservative governor.
That was the first time Andy mentioned issues with on demand, but
I do see it misbehave with the intel_cpufreq default sample period
(a.k.a sampling_rate) of 500uSec. See another e-mail I send in a moment.
... Doug
next prev parent reply other threads:[~2017-12-15 1:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HE1PR0402MB282866171A847AE244A9F76CF3340@HE1PR0402MB2828.eurprd04.prod.outlook.com>
2017-12-12 7:30 ` Ask for help on governor Viresh Kumar
2017-12-12 16:18 ` Doug Smythies
2017-12-12 16:51 ` Rafael J. Wysocki
2017-12-13 3:10 ` Doug Smythies
2017-12-13 6:17 ` Viresh Kumar
2017-12-13 6:22 ` Andy Tang
2017-12-13 6:55 ` Viresh Kumar
2017-12-13 16:13 ` Doug Smythies
2017-12-14 1:21 ` Doug Smythies
2017-12-14 2:42 ` Andy Tang
2017-12-14 18:25 ` Stratos Karafotis
2017-12-15 1:29 ` Doug Smythies [this message]
2017-12-15 1:30 ` Doug Smythies
2017-12-15 1:56 ` Andy Tang
2017-12-15 7:37 ` Doug Smythies
2017-12-15 9:00 ` Andy Tang
2017-12-15 14:26 ` Rafael J. Wysocki
2017-12-15 15:53 ` Rafael J. Wysocki
2017-12-15 18:27 ` Doug Smythies
2017-12-15 23:53 ` Rafael J. Wysocki
2017-12-18 1:15 ` [PATCH] cpufreq: governor: Ensure sufficiently large sampling intervals Rafael J. Wysocki
2017-12-18 2:59 ` Andy Tang
2017-12-18 4:38 ` Viresh Kumar
2017-12-18 16:11 ` Doug Smythies
2017-12-18 17:42 ` Rafael J. Wysocki
2017-12-13 16:13 ` Ask for help on governor Doug Smythies
2017-12-13 16:49 ` 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='001e01d37544$354e82c0$9feb8840$@net' \
--to=dsmythies@telus.net \
--cc=andy.tang@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stratosk@semaphore.gr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.