From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Prakash, Prashanth" <pprakash@codeaurora.org>,
George Cherian <george.cherian@cavium.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
viresh.kumar@linaro.org
Subject: Re: [PATCH v4] cpufreq / CPPC: Add cpuinfo_cur_freq support for CPPC
Date: Thu, 19 Jul 2018 12:46:17 +0200 [thread overview]
Message-ID: <1932970.0qede6EoN4@aspire.rjw.lan> (raw)
In-Reply-To: <41a6e3c7-db85-9ff1-daf4-07569c11fc8c@codeaurora.org>
On Saturday, July 14, 2018 12:20:43 AM CEST Prakash, Prashanth wrote:
> Hi George,
>
> This version looks good. Thanks!
>
> On 7/12/2018 12:07 AM, George Cherian wrote:
> > Per Section 8.4.7.1.3 of ACPI 6.2, The platform provides performance
> > feedback via set of performance counters. To determine the actual
> > performance level delivered over time, OSPM may read a set of
> > performance counters from the Reference Performance Counter Register
> > and the Delivered Performance Counter Register.
> >
> > OSPM calculates the delivered performance over a given time period by
> > taking a beginning and ending snapshot of both the reference and
> > delivered performance counters, and calculating:
> >
> > delivered_perf = reference_perf X (delta of delivered_perf counter / delta of reference_perf counter).
> >
> > Implement the above and hook this to the cpufreq->get method.
> >
> > Signed-off-by: George Cherian <george.cherian@cavium.com>
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> Acked-by: Prashanth Prakash <pprakash@codeaurora.org>
>
Patch applied, thanks!
prev parent reply other threads:[~2018-07-19 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 6:07 George Cherian
2018-07-13 22:20 ` Prakash, Prashanth
2018-07-19 10:46 ` Rafael J. Wysocki [this message]
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=1932970.0qede6EoN4@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=george.cherian@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pprakash@codeaurora.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®