From: "Prakash, Prashanth" <pprakash@codeaurora.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, viresh.kumar@linaro.org,
alexey.klimov@arm.com, hotran@apm.com, cov@codeaurora.org
Subject: Re: [PATCH] cpufreq: cpufreq_stats in the absence of frequency table
Date: Wed, 3 Aug 2016 09:41:21 -0600 [thread overview]
Message-ID: <a004f58d-d467-c2a4-ffa4-7179d628e8c8@codeaurora.org> (raw)
In-Reply-To: <4103198.vv1olU1ZFT@vostro.rjw.lan>
Hi Rafael,
On 8/2/2016 5:49 PM, Rafael J. Wysocki wrote:
> On Tuesday, August 02, 2016 05:41:24 PM Prakash, Prashanth wrote:
>> Hi Rafael,
>>
>> On 8/2/2016 5:27 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, August 02, 2016 05:18:57 PM Prashanth Prakash wrote:
>>>> cpufreq drivers such as CPPC works on contigious scale and does
>>>> not have a static frequency table. This commit adds cpufreq_stats
>>>> support for such drivers by creating a pseudo frequency table by
>>>> discretizing the contigious scale.
>>> No.
>>>
>>> And why?
>> The motivation is to be able to collect the frequency distribution data via
>> time_in_state sysfs entry as we can collect for other cpufreq drivers that
>> uses a frequency table.
> Which can be done by using the cpu_frequency trace point just fine, can't it?
Yes, but wanted to make sure existing userspace tools can be used with
platforms using CPPC as well.
> Plus, cpufreq_stats don't work with the schedutil governor and fast frequency
> switching anyway.
If we are expecting that usage of cpufreq_stats will slowly go away as we
switch to schedutil and more drivers enable fast_switching, then I agree
it doesn't make much sense to add support for cpufreq_stats.
Thanks,
Prashanth
next prev parent reply other threads:[~2016-08-03 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 23:18 [PATCH] cpufreq: cpufreq_stats in the absence of frequency table Prashanth Prakash
2016-08-02 23:27 ` Rafael J. Wysocki
2016-08-02 23:41 ` Prakash, Prashanth
2016-08-02 23:49 ` Rafael J. Wysocki
2016-08-03 15:41 ` Prakash, Prashanth [this message]
2016-08-03 21:41 ` Rafael J. Wysocki
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=a004f58d-d467-c2a4-ffa4-7179d628e8c8@codeaurora.org \
--to=pprakash@codeaurora.org \
--cc=alexey.klimov@arm.com \
--cc=cov@codeaurora.org \
--cc=hotran@apm.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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