From: Seiichi Ikarashi <s.ikarashi@jp.fujitsu.com>
To: "Chen, Yu C" <yu.c.chen@intel.com>
Cc: "kristen@linux.intel.com" <kristen@linux.intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: [PATCH] intel_pstate: prevent max_perf_pct < min_perf_pct
Date: Wed, 9 Sep 2015 13:27:17 +0900 [thread overview]
Message-ID: <55EFB525.3010705@jp.fujitsu.com> (raw)
In-Reply-To: <36DF59CE26D8EE47B0655C516E9CE6401D4A70BF@SHSMSX101.ccr.corp.intel.com>
Hi, Yu
On 2015-09-08 16:27, Chen, Yu C wrote:
> Hi, Seiichi
>
>>> I guess a similar patch has been sent at:
>>> https://patchwork.kernel.org/patch/6995461/
>>
>> Yes, your patch looks better than mine from the point of view of covering
>> intel_pstate_set_policy().
>>
>> Still I have a question.
>> Does your patch allow the following condition?
>>
>> limits.max_policy_pct > limits.min_perf_pct > limits.max_perf_pct >
>> limits.min_policy_pct
>>
>
> Thanks! Seems my previous patch does not guarantee
> max_perf_pct >= min_perf_pct, I think following logic would be better:
> Step0: normalize the user input to [min_policy, max_policy]
> Step1: make sure max_perf_pct>= min_perf_pct
>
> BTW,why I add step0 here is because we should not rely on user input, and
> different policy might have different (min,max), for example,
> max_policy_pct=40,min_policy_pct=30, and user input of
> echo 50 > min_sysfs_pct would make the final min_perf_pct to
> 50, it's not in legal policy scope, so...
Those two steps will make sense.
I will review your upcoming v2 patch.
Regards,
Seiichi
prev parent reply other threads:[~2015-09-09 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 10:58 [PATCH] intel_pstate: prevent max_perf_pct < min_perf_pct Seiichi Ikarashi
2015-09-07 9:00 ` Chen, Yu C
2015-09-07 21:46 ` Rafael J. Wysocki
2015-09-07 23:18 ` Seiichi Ikarashi
2015-09-08 7:27 ` Chen, Yu C
2015-09-09 4:27 ` Seiichi Ikarashi [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=55EFB525.3010705@jp.fujitsu.com \
--to=s.ikarashi@jp.fujitsu.com \
--cc=kristen@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--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.