From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Mike Chan <mike@android.com>
Cc: "tj@kernel.org" <tj@kernel.org>,
"Miller@fmi.uni-stuttgart.de" <Miller@fmi.uni-stuttgart.de>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] cpufreq: ondemand: Refactor frequency increase code
Date: Tue, 26 Jan 2010 11:31:34 -0800 [thread overview]
Message-ID: <1264534294.16916.345.camel@localhost.localdomain> (raw)
In-Reply-To: <1264470435-14739-1-git-send-email-mike@android.com>
On Mon, 2010-01-25 at 17:47 -0800, Mike Chan wrote:
> Make simpler to read and call.
>
> Signed-off-by: Mike Chan <mike@android.com>
Nack.
This patch seem to be changing the logic in the code. Comment inlined
below.
> ---
> drivers/cpufreq/cpufreq_ondemand.c | 26 +++++++++++++-------------
> 1 files changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/cpufreq/cpufreq_ondemand.c b/drivers/cpufreq/cpufreq_ondemand.c
> index 4b34ade..3dcf126 100644
> --- a/drivers/cpufreq/cpufreq_ondemand.c
> +++ b/drivers/cpufreq/cpufreq_ondemand.c
> @@ -443,6 +443,17 @@ static struct attribute_group dbs_attr_group_old = {
>
> /************************** sysfs end ************************/
>
> +static int dbs_freq_increase(struct cpufreq_policy *p, unsigned int target_freq)
> +{
> + if (dbs_tuners_ins.powersave_bias)
> + target_freq = powersave_bias_target(p, target_freq,
> + CPUFREQ_RELATION_H);
> +
> + __cpufreq_driver_target(p, target_freq,
> + dbs_tuners_ins.powersave_bias ?
> + CPUFREQ_RELATION_L : CPUFREQ_RELATION_H);
> +}
> +
> static void dbs_check_cpu(struct cpu_dbs_info_s *this_dbs_info)
> {
> unsigned int max_load_freq;
> @@ -520,19 +531,8 @@ static void dbs_check_cpu(struct cpu_dbs_info_s *this_dbs_info)
>
> /* Check for frequency increase */
> if (max_load_freq > dbs_tuners_ins.up_threshold * policy->cur) {
> - /* if we are already at full speed then break out early */
> - if (!dbs_tuners_ins.powersave_bias) {
> - if (policy->cur == policy->max)
> - return;
> -
> - __cpufreq_driver_target(policy, policy->max,
> - CPUFREQ_RELATION_H);
> - } else {
> - int freq = powersave_bias_target(policy, policy->max,
> - CPUFREQ_RELATION_H);
> - __cpufreq_driver_target(policy, freq,
> - CPUFREQ_RELATION_L);
> - }
> + if (policy->cur != policy->max)
> + dbs_freq_increase(policy, policy->max);
In case of powersave_bias, bias_target and driver_target was getting
called even for cur == max before. After this change, they wont be
getting called, which would be wrong.
Thanks,
Venki
prev parent reply other threads:[~2010-01-26 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 1:47 [PATCH v2 1/2] cpufreq: ondemand: Refactor frequency increase code Mike Chan
2010-01-26 1:47 ` [PATCH v2 2/2] cpufreq: ondemand: Independent max speed for nice threads with nice_max_freq Mike Chan
2010-01-28 0:17 ` Andrew Morton
2010-01-26 19:31 ` Pallipadi, Venkatesh [this message]
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=1264534294.16916.345.camel@localhost.localdomain \
--to=venkatesh.pallipadi@intel.com \
--cc=Miller@fmi.uni-stuttgart.de \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@android.com \
--cc=tj@kernel.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).