From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Joe Konno <joe.konno@linux.intel.com>
Cc: linux-pm@vger.kernel.org, viresh.kumar@linaro.org,
linux-kernel@vger.kernel.org, kristen@linux.intel.com
Subject: Re: [PATCH] intel_pstate: set BYT MSR with wrmsrl_on_cpu()
Date: Thu, 07 May 2015 22:58:11 +0200 [thread overview]
Message-ID: <2313402.8O0OJYkUeN@vostro.rjw.lan> (raw)
In-Reply-To: <1431017979-28349-1-git-send-email-joe.konno@linux.intel.com>
On Thursday, May 07, 2015 09:59:39 AM Joe Konno wrote:
> From: Joe Konno <joe.konno@intel.com>
>
> In instances where the default cpufreq governor is Performance, reading
I'm not really sure what this is about. You're talking about cpufreq governors
and this is an intel_pstate patch. What gives?
> from MSR 0x199 on an applicable multi-core Atom system saw boot-to-boot
> variability in the P-State value set to each logical core. Sometimes
> only one logical core would be set properly, other times two or three.
> There was an assumption in the code that only a thread on the intended
> logical core would be calling the wrmsrl() function. That was disproven
> during debug, as cpufreq, at init, was not always calling from the same
> as the logical core it targeted. Thus, use wrmsrl_on_cpu() instead, as
> done in the core_set_pstate() function.
>
> For: LCK-1822
This tag is meaningless upstream.
> Fixes: 007bea098b86 ("intel_pstate: Add setting voltage value for
> baytrail P states.")
So, you're fixing a function introduced by the above commit, right?
> Signed-off-by: Joe Konno <joe.konno@intel.com>
> ---
> drivers/cpufreq/intel_pstate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> index 6414661ac1c4..c45d274a75c8 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -535,7 +535,7 @@ static void byt_set_pstate(struct cpudata *cpudata, int pstate)
>
> val |= vid;
>
> - wrmsrl(MSR_IA32_PERF_CTL, val);
> + wrmsrl_on_cpu(cpudata->cpu, MSR_IA32_PERF_CTL, val);
So the bug is that this may run on a CPU which is not cpudata->cpu in which
case the write will not happen where it should. Is that correct?
> }
>
> #define BYT_BCLK_FREQS 5
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2015-05-07 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 16:59 Joe Konno
2015-05-07 20:58 ` Rafael J. Wysocki [this message]
2015-05-07 23:22 ` Joe Konno
2015-05-08 13:59 ` Rafael J. Wysocki
2015-05-11 18:39 ` Kristen Carlson Accardi
2015-05-12 14:59 ` Joe Konno
2015-05-15 0:13 ` Rafael J. Wysocki
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=2313402.8O0OJYkUeN@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=joe.konno@linux.intel.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®