From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: dirk.brandewie@gmail.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, rafael.j.wysocki@intel.com,
gf435@gmx.net, bp@alien8.de,
Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: [PATCH] intel_pstate: Change busy calculation to use fixed point math.
Date: Wed, 26 Feb 2014 01:39:25 +0100 [thread overview]
Message-ID: <1509075.br8MLUFIAK@vostro.rjw.lan> (raw)
In-Reply-To: <1393353337-19778-1-git-send-email-dirk.j.brandewie@intel.com>
On Tuesday, February 25, 2014 10:35:37 AM dirk.brandewie@gmail.com wrote:
> From: Dirk Brandewie <dirk.j.brandewie@intel.com>
>
> Commit fcb6a15c2e Take core C0 time into account for core busy calculation.
>
> Introduced a regression on some processor SKUs supported by
> intel_pstate. This was caused by the truncation caused by using
> integer math to calculate core busy and C0 percentages.
>
> On a i7-4770K processor operating at 800Mhz going to 100% utilization
> the percent busy of the CPU using integer math is 22% it actually is
> 22.85%. This value scaled to the current frequency returned 97 which
> the PID interpreted as no error and did not adjust the P state.
>
> Tested on i7-4770K, i7-2600, i5-3230M
>
> References:
> https://lkml.org/lkml/2014/2/19/626
> https://bugzilla.kernel.org/show_bug.cgi?id=70941
>
> Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
Queued up as a fix for 3.14.
Thanks!
> ---
> drivers/cpufreq/intel_pstate.c | 28 ++++++++++++++++++----------
> 1 file changed, 18 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> index e908161..2cd36b9 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -39,9 +39,10 @@
> #define BYT_TURBO_RATIOS 0x66c
>
>
> -#define FRAC_BITS 8
> +#define FRAC_BITS 6
> #define int_tofp(X) ((int64_t)(X) << FRAC_BITS)
> #define fp_toint(X) ((X) >> FRAC_BITS)
> +#define FP_ROUNDUP(X) ((X) += 1 << FRAC_BITS)
>
> static inline int32_t mul_fp(int32_t x, int32_t y)
> {
> @@ -556,18 +557,20 @@ static void intel_pstate_get_cpu_pstates(struct cpudata *cpu)
> static inline void intel_pstate_calc_busy(struct cpudata *cpu,
> struct sample *sample)
> {
> - u64 core_pct;
> - u64 c0_pct;
> + int32_t core_pct;
> + int32_t c0_pct;
>
> - core_pct = div64_u64(sample->aperf * 100, sample->mperf);
> + core_pct = div_fp(int_tofp((sample->aperf)),
> + int_tofp((sample->mperf)));
> + core_pct = mul_fp(core_pct, int_tofp(100));
> + FP_ROUNDUP(core_pct);
> +
> + c0_pct = div_fp(int_tofp(sample->mperf), int_tofp(sample->tsc));
>
> - c0_pct = div64_u64(sample->mperf * 100, sample->tsc);
> sample->freq = fp_toint(
> - mul_fp(int_tofp(cpu->pstate.max_pstate),
> - int_tofp(core_pct * 1000)));
> + mul_fp(int_tofp(cpu->pstate.max_pstate * 1000), core_pct));
>
> - sample->core_pct_busy = mul_fp(int_tofp(core_pct),
> - div_fp(int_tofp(c0_pct + 1), int_tofp(100)));
> + sample->core_pct_busy = mul_fp(core_pct, c0_pct);
> }
>
> static inline void intel_pstate_sample(struct cpudata *cpu)
> @@ -579,6 +582,10 @@ static inline void intel_pstate_sample(struct cpudata *cpu)
> rdmsrl(MSR_IA32_MPERF, mperf);
> tsc = native_read_tsc();
>
> + aperf = aperf >> FRAC_BITS;
> + mperf = mperf >> FRAC_BITS;
> + tsc = tsc >> FRAC_BITS;
> +
> cpu->sample_ptr = (cpu->sample_ptr + 1) % SAMPLE_COUNT;
> cpu->samples[cpu->sample_ptr].aperf = aperf;
> cpu->samples[cpu->sample_ptr].mperf = mperf;
> @@ -610,7 +617,8 @@ static inline int32_t intel_pstate_get_scaled_busy(struct cpudata *cpu)
> core_busy = cpu->samples[cpu->sample_ptr].core_pct_busy;
> max_pstate = int_tofp(cpu->pstate.max_pstate);
> current_pstate = int_tofp(cpu->pstate.current_pstate);
> - return mul_fp(core_busy, div_fp(max_pstate, current_pstate));
> + core_busy = mul_fp(core_busy, div_fp(max_pstate, current_pstate));
> + return FP_ROUNDUP(core_busy);
> }
>
> static inline void intel_pstate_adjust_busy_pstate(struct cpudata *cpu)
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-02-26 0:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 22:47 Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks Greg KH
2014-02-20 0:03 ` Dirk Brandewie
2014-02-20 0:35 ` Greg KH
2014-02-20 0:51 ` Greg KH
2014-02-20 14:56 ` Dirk Brandewie
2014-02-20 18:10 ` Greg KH
2014-02-24 22:37 ` Greg KH
2014-02-24 23:03 ` Dirk Brandewie
2014-02-25 18:35 ` [PATCH] intel_pstate: Change busy calculation to use fixed point math dirk.brandewie
2014-02-26 0:39 ` Rafael J. Wysocki [this message]
2014-02-26 14:57 ` Otto Meier
2014-02-28 22:47 ` Greg KH
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=1509075.br8MLUFIAK@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=bp@alien8.de \
--cc=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=gf435@gmx.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@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
all inboxes | Powered by JetHome®