All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Chen, Yu C" <yu.c.chen@intel.com>,
	"dsmythies@telus.net" <dsmythies@telus.net>
Cc: "Brown, Len" <len.brown@intel.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"rafael@kernel.org" <rafael@kernel.org>
Subject: Re: [PATCH v2] Documentation: cpufreq: intel_pstate: enhance documentation
Date: Mon, 28 Dec 2015 16:44:16 -0800	[thread overview]
Message-ID: <5681D760.6090309@linux.intel.com> (raw)
In-Reply-To: <36DF59CE26D8EE47B0655C516E9CE6402869140A@shsmsx102.ccr.corp.intel.com>



On 12/28/2015 04:17 PM, Chen, Yu C wrote:
> Hi,
>
>> -----Original Message-----
>> From: linux-pm-owner@vger.kernel.org [mailto:linux-pm-
>> owner@vger.kernel.org] On Behalf Of Srinivas Pandruvada
>> Sent: Tuesday, December 29, 2015 2:15 AM
>> To: rafael@kernel.org; dsmythies@telus.net
>> Cc: Brown, Len; linux-pm@vger.kernel.org; Srinivas Pandruvada
>> Subject: [PATCH v2] Documentation: cpufreq: intel_pstate: enhance
>> documentation
>>
>> This is an attempt to make documentation more user friendly.
>>
>> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>> ---
>> Changes in v2:
>> 	Suggested by Doug Smythies
>> 		- Grammar correction
>> 		- Use default PID and impact of setpoint on ramp up times
>>
>>
>>   Documentation/cpu-freq/intel-pstate.txt | 193
>> +++++++++++++++++++++++++-------
>>   1 file changed, 151 insertions(+), 42 deletions(-)
>>
>> diff --git a/Documentation/cpu-freq/intel-pstate.txt b/Documentation/cpu-
>> freq/intel-pstate.txt
>> index be8d400..5398a66 100644
>> --- a/Documentation/cpu-freq/intel-pstate.txt
>> +++ b/Documentation/cpu-freq/intel-pstate.txt
>> @@ -1,61 +1,131 @@
>> -Intel P-state driver
>> +Intel P-State driver
>>   --------------------
>>
>> +For the same load at setpoint = 60, this will result in the next
>> +P-State = 0x08 - ((60 - 100) * 0.2) = 16 So by changing the setpoint
>> +from 97 to 60, there is an increase of the next P-State from 9 to 16.
>> +So this will make processor execute at higher P-State for the same CPU
>> +load. If the load continues to be more than the setpoint during next
>> +sample intervals, then P-State will go up again till the maximum
>> +P-State is reached. But the ramp up time to reach the maximum P-State
>> +will be much faster when the setpoint is 60 compared to 97.
>> --
> Just inspired by another thread in the maillist, how about adding a description
> on suggesting  enable the ftrace  when user is trying to do some debug/tuning?
>

Good idea. Will add to next version.

Thanks,
Srinivas


> thanks,
> yu
> N�����r��y���b�X��ǧv�^�)޺{.n�+����{��h��\x17��ܨ}���Ơz�&j:+v���\a����zZ+��+zf���h���~����i���z�\x1e�w���?����&�)ߢ^[fl===
>

      reply	other threads:[~2015-12-29  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 18:15 [PATCH v2] Documentation: cpufreq: intel_pstate: enhance documentation Srinivas Pandruvada
2015-12-29  0:17 ` Chen, Yu C
2015-12-29  0:44   ` Srinivas Pandruvada [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=5681D760.6090309@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=dsmythies@telus.net \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=yu.c.chen@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 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.