From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Philippe Longepe <philippe.longepe@linux.intel.com>
Cc: linux-pm@vger.kernel.org,
Stephane Gasparini <stephane.gasparini@linux.intel.com>
Subject: Re: [PATCH v1 1/2] intel_pstate: Use the cpu load to determine the PercentPerformance
Date: Fri, 06 Nov 2015 17:14:28 -0800 [thread overview]
Message-ID: <1446858868.5023.6.camel@linux.intel.com> (raw)
In-Reply-To: <1546343.Y03T7q8XC6@vostro.rjw.lan>
On Sat, 2015-11-07 at 02:09 +0100, Rafael J. Wysocki wrote:
> On Tuesday, November 03, 2015 10:27:19 AM Philippe Longepe wrote:
> > Aperf and Mperf counter are not enough to determine the Target P
> > -state
> > because they measure performance only when the targeted processor
> > is
> > in the C0 state (active state).
> > Because of that, we were computing the average P-state during the
> > last
> > period which can be very different from the average frequency
> > (or percentage of performance).
> >
> > As defined in the SDM (section 14.2), the PercentPerformance is
> > defined by:
> >
> > PercentPerformance = PercentBusy * (delta_aperf / delta_mperf);
> >
> > The PercentBusy (or load) can be estimated as the ratio of the
> > mperf
> > counter running at a constant frequency only during active periods
> > (C0)
> > and the time stamp counter running at the same frequency but also
> > during idle.
> >
> > So, PercentBusy = 100 * (delta_mperf / delta_tsc)
> >
> > and, PercentPerformance = 100 * (delta_mperf / delta_tsc) *
> > (delta_aperf / delta_mperf)
> > That can be simplified with:
> > PercentPerformance = 100 * (delta_aperf / delta_tsc)
> >
> > Signed-off-by: Philippe Longepe <philippe.longepe@linux.intel.com>
> > Signed-off-by: Stephane Gasparini <
> > stephane.gasparini@linux.intel.com>
>
> Srinivas, I need your ACK here and for the [2/2].
>
These needs further validation to merge to upstream kernel.
Thanks,
Srinivas
> Thanks,
> Rafael
>
next prev parent reply other threads:[~2015-11-07 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 9:27 [PATCH v1 1/2] intel_pstate: Use the cpu load to determine the PercentPerformance Philippe Longepe
2015-11-03 9:27 ` [PATCH v1 2/2] intel_pstate: Change the setpoint for the cores Philippe Longepe
2015-11-21 16:22 ` Doug Smythies
2015-11-23 13:45 ` Philippe Longepe
2015-11-07 1:09 ` [PATCH v1 1/2] intel_pstate: Use the cpu load to determine the PercentPerformance Rafael J. Wysocki
2015-11-07 1:14 ` Srinivas Pandruvada [this message]
2015-11-21 16:21 ` Doug Smythies
2015-11-23 13:28 ` plongepe
2015-11-24 1:33 ` Doug Smythies
2015-11-24 1:44 ` 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=1446858868.5023.6.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=philippe.longepe@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=stephane.gasparini@linux.intel.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;
as well as URLs for NNTP newsgroup(s).