From: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] cpufreq: conservative: Fix requested_freq handling
Date: Mon, 8 Oct 2018 17:09:00 +0200 [thread overview]
Message-ID: <20181008150901.19667-1-waldemar.rymarkiewicz@gmail.com> (raw)
From: Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>
The governor updates dbs_info->requested_freq only after increasing or
decreasing frequency. There is, however, an use case when this is not
sufficient.
Imagine, external module constraining cpufreq policy in a way that policy->max
= policy->min = max_available_freq (eg. 1Ghz). CPUfreq will set freq to
max_freq and conservative gov will not try downscale/upscale due to the
limits. It will just exit instead
if (requested_freq > policy->max || requested_freq < policy->min)
//max=min=1Ghz -> requested_freq=cur=1Ghz
requested_freq = policy->cur;
[...]
if (requested_freq == policy->max)
goto out;
In a result, dbs_info->requested_freq is not updated with newly calculated
requested_freq=1Ghz. Next, execution of update routine will use again
previously stored requested_freq (in my case it was min_available_freq)
[...]
unsigned int requested_freq = dbs_info->requested_freq;
[....]
Now, when external module returns to previous policy limits that is
policy->min = min_available_freq and policy->max = max_available_freq,
conservative governor is not able to decrease frequency because stored
requested_freq is still or rather already set to min_available_freq so
the check (for decreasing)
[...]
if (load < cs_tuners->down_threshold) {
[....]
if (requested_freq == policy->min)
goto out;
[...]
returns from routine before it does any freq change. To fix that just update
dbs_info->requested_freq every time we go out from the update routine.
Signed-off-by: Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>
---
drivers/cpufreq/cpufreq_conservative.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/cpufreq/cpufreq_conservative.c b/drivers/cpufreq/cpufreq_conservative.c
index f20f20a..7f90f6e 100644
--- a/drivers/cpufreq/cpufreq_conservative.c
+++ b/drivers/cpufreq/cpufreq_conservative.c
@@ -113,7 +113,6 @@ static unsigned int cs_dbs_update(struct cpufreq_policy *policy)
requested_freq = policy->max;
__cpufreq_driver_target(policy, requested_freq, CPUFREQ_RELATION_H);
- dbs_info->requested_freq = requested_freq;
goto out;
}
@@ -136,10 +135,10 @@ static unsigned int cs_dbs_update(struct cpufreq_policy *policy)
requested_freq = policy->min;
__cpufreq_driver_target(policy, requested_freq, CPUFREQ_RELATION_L);
- dbs_info->requested_freq = requested_freq;
}
out:
+ dbs_info->requested_freq = requested_freq;
return dbs_data->sampling_rate;
}
--
2.10.1
next reply other threads:[~2018-10-08 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 15:09 Waldemar Rymarkiewicz [this message]
2018-10-09 7:47 ` [PATCH] cpufreq: conservative: Fix requested_freq handling Rafael J. Wysocki
2018-10-09 16:06 ` Waldemar Rymarkiewicz
2018-10-11 21:06 ` Rafael J. Wysocki
2018-10-15 9:34 ` Waldemar Rymarkiewicz
2018-10-15 11:31 ` Rafael J. Wysocki
2018-10-15 12:50 ` Waldemar Rymarkiewicz
2018-10-15 21:03 ` Rafael J. Wysocki
2018-10-15 21:21 ` [PATCH] cpufreq: conservative: Take limits changes into account properly Rafael J. Wysocki
2018-10-16 6:38 ` Waldemar Rymarkiewicz
2018-10-16 9:52 ` 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=20181008150901.19667-1-waldemar.rymarkiewicz@gmail.com \
--to=waldemar.rymarkiewicz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=waldemarx.rymarkiewicz@intel.com \
/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