From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Huaisheng HS1 Ye <yehs1@lenovo.com>
Cc: "srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: intel_pstate: Fix cpuinfo_cur_freq after performance governor changes
Date: Mon, 24 Jul 2017 13:36:15 +0200 [thread overview]
Message-ID: <7185077.O26hx51RqR@aspire.rjw.lan> (raw)
In-Reply-To: <1500875013-123321-1-git-send-email-yehs1@lenovo.com>
On Monday, July 24, 2017 05:43:14 AM Huaisheng HS1 Ye wrote:
> After commit 82b4e03e01bc (intel_pstate: skip scheduler hook when
> in "performance" mode) Software P-state control modes couldn't get
> dynamic value during performance mode,
Please explain what you mean here.
I guess you carried out some tests and the results were not as expected,
so what was the test?
> and it still in last value from powersave mode, so clear its value to get
> same behavior as Hardware P-state to avoid confusion.
And please explain why it should be fixed the way you've done that.
> Signed-off-by: Huaisheng Ye <yehs1@lenovo.com>
> ---
> drivers/cpufreq/intel_pstate.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> index 6cd5035..c675626 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -2050,6 +2050,7 @@ static int intel_pstate_set_policy(struct cpufreq_policy *policy)
> */
> intel_pstate_clear_update_util_hook(policy->cpu);
> intel_pstate_max_within_limits(cpu);
> + cpu->sample.core_avg_perf = 0;
> } else {
> intel_pstate_set_update_util_hook(policy->cpu);
> }
>
next prev parent reply other threads:[~2017-07-24 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 5:43 [PATCH] cpufreq: intel_pstate: Fix cpuinfo_cur_freq after performance governor changes Huaisheng HS1 Ye
2017-07-24 11:36 ` Rafael J. Wysocki [this message]
2017-07-24 15:32 ` Huaisheng HS1 Ye
2017-07-24 23:51 ` Rafael J. Wysocki
2017-07-25 1:46 ` Huaisheng HS1 Ye
2017-07-25 2:57 ` Srinivas Pandruvada
2017-07-25 7:03 ` Huaisheng HS1 Ye
2017-07-25 14:37 ` Srinivas Pandruvada
2017-07-25 15:22 ` Huaisheng HS1 Ye
2017-07-25 21:46 ` Rafael J. Wysocki
2017-07-25 15:35 ` Rafael J. Wysocki
2017-07-25 22:42 ` [PATCH] cpufreq: intel_pstate: Drop ->get from intel_pstate structure Rafael J. Wysocki
2017-07-27 3:47 ` 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=7185077.O26hx51RqR@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=viresh.kumar@linaro.org \
--cc=yehs1@lenovo.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