From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Alexandra Yates <alexandra.yates@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] SKL intel_pstate update MSR values when changing governors
Date: Tue, 24 Nov 2015 07:57:42 -0800 [thread overview]
Message-ID: <1448380662.3070.3.camel@linux.intel.com> (raw)
In-Reply-To: <8282537.nh6Mqkv7tq@vostro.rjw.lan>
On Tue, 2015-11-24 at 15:28 +0100, Rafael J. Wysocki wrote:
> On Monday, November 23, 2015 05:17:36 PM Srinivas Pandruvada wrote:
> > On Tue, 2015-11-24 at 02:09 +0100, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > On Sat, Nov 21, 2015 at 1:16 AM, Srinivas Pandruvada
> > > <srinivas.pandruvada@linux.intel.com> wrote:
> > > >
>
> [cut]
>
> > >
> > > > > For more information on the MSR values for SKL please visit
> > > > > ISDM under Managing HWP.
> > > > >
> > > > > Signed-off-by: Alexandra Yates <
> > > > > alexandra.yates@linux.intel.com>
> > > >
> > > > Acked-by: Srinivas Pandruvada <
> > > > srinivas.pandruvada@linux.intel.com>
> > > > >
> > > > > ---
> > > > > drivers/cpufreq/intel_pstate.c | 2 ++
> > > > > 1 file changed, 2 insertions(+)
> > > > >
> > > > > diff --git a/drivers/cpufreq/intel_pstate.c
> > > > > b/drivers/cpufreq/intel_pstate.c
> > > > > index 2e31d09..0eeb7da 100644
> > > > > --- a/drivers/cpufreq/intel_pstate.c
> > > > > +++ b/drivers/cpufreq/intel_pstate.c
> > > > > @@ -1242,6 +1242,8 @@ static int
> > > > > intel_pstate_set_policy(struct
> > > > > cpufreq_policy *policy)
> > > > > policy->max >= policy->cpuinfo.max_freq) {
> > > > > pr_debug("intel_pstate: set performance\n");
> > > > > limits = &performance_limits;
> > > > > + if (hwp_active)
> > > > > + intel_pstate_hwp_set();
> > >
> > > Honestly, I'm not really sure how this is matching the changelog.
> > >
> > > What it does is to ensure that the correct limits are used when
> > > in the
> > > HWP mode too as far as I can say. Is my understanding correct
> > > here?
> > Yes.
>
> OK
>
> But if we make the "performance" limits take effect here, it will
> effectively
> make HWP use min = max = 100%, right? Is that what we want to happen
> here?
Yes. intel_pstate_hwp_set() uses limits->min_perf_pct and limits
->max_perf_pct to set HWP limits. Here these will be set to 100%.
Thanks,
Srinivas
>
> Thanks,
> Rafael
>
next prev parent reply other threads:[~2015-11-24 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SKL intel_pstate update MSR values when changing governors>
2015-11-18 1:58 ` [PATCH V2] SKL intel_pstate update MSR values when changing governors Alexandra Yates
2015-11-18 2:15 ` Srinivas Pandruvada
2015-11-18 22:58 ` [PATCH V3] " Alexandra Yates
2015-11-21 0:16 ` Srinivas Pandruvada
2015-11-24 1:09 ` Rafael J. Wysocki
2015-11-24 1:17 ` Srinivas Pandruvada
2015-11-24 14:28 ` Rafael J. Wysocki
2015-11-24 15:57 ` Srinivas Pandruvada [this message]
2015-11-24 16:36 ` Rafael J. Wysocki
2015-11-24 16:27 ` Srinivas Pandruvada
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=1448380662.3070.3.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=alexandra.yates@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.