From: Stratos Karafotis <stratosk@semaphore.gr>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Dirk Brandewie <dirk.j.brandewie@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/7] cpufreq: intel_pstate: Simplify code in intel_pstate_adjust_busy_pstate
Date: Tue, 10 Jun 2014 17:51:58 +0300 [thread overview]
Message-ID: <53971B8E.4040302@semaphore.gr> (raw)
In-Reply-To: <CAKohpokYB4oKxrEwHH888T5hg=zrpb0PCs_QKTLS0bd-_fqeTA@mail.gmail.com>
On 10/06/2014 08:27 πμ, Viresh Kumar wrote:
> On 10 June 2014 02:30, Stratos Karafotis <stratosk@semaphore.gr> wrote:
>> Simplify the code by removing the inline functions
>> pstate_increase and pstate_decrease and use directly the
>> intel_pstate_set_pstate.
>>
>> Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
>> ---
>> drivers/cpufreq/intel_pstate.c | 26 +++-----------------------
>> 1 file changed, 3 insertions(+), 23 deletions(-)
>>
>> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
>> index 3a49269..26a0262 100644
>> --- a/drivers/cpufreq/intel_pstate.c
>> +++ b/drivers/cpufreq/intel_pstate.c
>> @@ -588,21 +588,6 @@ static void intel_pstate_set_pstate(struct cpudata *cpu, int pstate)
>> pstate_funcs.set(cpu, pstate);
>> }
>>
>> -static inline void intel_pstate_pstate_increase(struct cpudata *cpu, int steps)
>> -{
>> - int target;
>> - target = cpu->pstate.current_pstate + steps;
>> -
>> - intel_pstate_set_pstate(cpu, target);
>> -}
>> -
>> -static inline void intel_pstate_pstate_decrease(struct cpudata *cpu, int steps)
>> -{
>> - int target;
>> - target = cpu->pstate.current_pstate - steps;
>> - intel_pstate_set_pstate(cpu, target);
>> -}
>> -
>> static void intel_pstate_get_cpu_pstates(struct cpudata *cpu)
>> {
>> cpu->pstate.min_pstate = pstate_funcs.get_min();
>> @@ -695,20 +680,15 @@ static inline void intel_pstate_calc_scaled_busy(struct cpudata *cpu)
>> static inline void intel_pstate_adjust_busy_pstate(struct cpudata *cpu)
>> {
>> struct _pid *pid;
>> - signed int ctl = 0;
>> - int steps;
>> + signed int ctl;
>>
>> pid = &cpu->pid;
>> intel_pstate_calc_scaled_busy(cpu);
>>
>> ctl = pid_calc(pid, cpu->sample.busy_scaled);
>>
>> - steps = abs(ctl);
>> -
>> - if (ctl < 0)
>> - intel_pstate_pstate_increase(cpu, steps);
>> - else
>> - intel_pstate_pstate_decrease(cpu, steps);
>> + /* Negative values of ctl increase the pstate and vice versa */
>> + intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate - ctl);
>> }
>
> I am not very good at this driver but there is some obvious functional
> change here. Earlier we used to pass
> 'cpu->pstate.current_pstate {-|+} steps' and now you are doing '-ctl' only
>
The original code is:
if (ctl < 0)
intel_pstate_pstate_increase(cpu, steps);
else
intel_pstate_pstate_decrease(cpu, steps);
Without inlines functions intel_pstate_pstate_increase() and
intel_pstate_pstate_decrease() we get:
if (ctl < 0)
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate + steps);
else
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate - steps);
But steps = abs(ctl), so:
if (ctl < 0)
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate + abs(ctl));
else
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate - abs(ctl));
By definition, abs(ctl) = ctl if ctl >= 0, -ctl if ctl < 0. Thus:
if (ctl < 0)
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate + (-ctl));
else
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate - ctl);
And:
if (ctl < 0)
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate - ctl);
else
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate - ctl);
Finally remove the unnecessary if statement.
intel_pstate_set_pstate(cpu, cpu->pstate.current_pstate - ctl);
So, this is equivalent with the original code.
Thanks,
Stratos
next prev parent reply other threads:[~2014-06-10 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 21:00 [PATCH 4/7] cpufreq: intel_pstate: Simplify code in intel_pstate_adjust_busy_pstate Stratos Karafotis
2014-06-10 5:27 ` Viresh Kumar
2014-06-10 14:51 ` Stratos Karafotis [this message]
2014-06-10 17:07 ` Dirk Brandewie
2014-06-10 17:48 ` Stratos Karafotis
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=53971B8E.4040302@semaphore.gr \
--to=stratosk@semaphore.gr \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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