From: Viresh Kumar <viresh.kumar@linaro.org>
To: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] cpufreq: powernv: Use PMSR to verify global and local pstate
Date: Fri, 4 Nov 2016 12:11:32 +0530 [thread overview]
Message-ID: <20161104064132.GB3414@vireshk-i7> (raw)
In-Reply-To: <1478237255-4258-2-git-send-email-akshay.adiga@linux.vnet.ibm.com>
On 04-11-16, 10:57, Akshay Adiga wrote:
> As fast_switch may get called in interrupt disable mode, it does not
s/in interrupt disable mode/with interrupts disabled
s/it does/it may
> update the global_pstate_info data structure. Hence the global_pstate_info
> has stale data whenever pstate is updated through fast_swtich().
s/has/may have
s/swtich/switch
>
> So the gpstate_timer can fire after a fast_switch() call has update
s/So the/The
s/a fast_swtich() call has update/the fast_switch() call has updated
> the pstates to a different value. Hence the timer handler cannot rely
> on the cached values of local and global pstate and needs to read it
> from the PMSR.
>
> Signed-off-by: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
>
> ---
> drivers/cpufreq/powernv-cpufreq.c | 32 ++++++++++++++++++++++----------
> 1 file changed, 22 insertions(+), 10 deletions(-)
I am not the best guy to judge the code changes here. Can you please include
Shilpa and Gautham to the mail chain and get there feedback.
--
viresh
next prev parent reply other threads:[~2016-11-04 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 5:27 [PATCH 1/2] cpufreq: powernv: Adding fast_switch for schedutil Akshay Adiga
2016-11-04 5:27 ` [PATCH 2/2] cpufreq: powernv: Use PMSR to verify global and local pstate Akshay Adiga
2016-11-04 6:41 ` Viresh Kumar [this message]
2016-11-07 7:32 ` Akshay Adiga
2016-11-04 6:33 ` [PATCH 1/2] cpufreq: powernv: Adding fast_switch for schedutil Viresh Kumar
2016-11-07 7:32 ` Akshay Adiga
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=20161104064132.GB3414@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).