linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	linux-kernel@vger.kernel.org,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Myungjoo Ham <myungjoo.ham@samsung.com>
Subject: Re: [PATCH v2] cpufreq: stats: Add 'load_table' debugfs file to show accumulated data of CPUs
Date: Mon, 24 Jun 2013 17:32:09 +0900	[thread overview]
Message-ID: <51C80409.1040806@samsung.com> (raw)
In-Reply-To: <5527616.jZ71Fx7IV6@vostro.rjw.lan>

On 06/21/2013 10:13 PM, Rafael J. Wysocki wrote:
> On Friday, June 21, 2013 01:01:35 PM Chanwoo Choi wrote:
>> On 06/21/2013 12:42 AM, Viresh Kumar wrote:
>>> On 20 June 2013 16:48, Chanwoo Choi <cw00.choi@samsung.com> wrote:
>>>> But,
>>>> To show old frequency/new frequency on load_table debugfs file,
>>>> governor function(dbs_check_cpu()) pass calculated CPUs load to specific governor(e.g., ondemand)
>>>> as below function flow.
>>>>
>>>> dbs_check_cpu() (in cpufreq.c)
>>>> -> od_check_cpu() (in cpufreq_ondemand.c)
>>>> -> __cpufreq_driver_target() (in cpufreq.c)
>>>> -> cpufreq_driver->target(policy)
>>>>
>>>> Also, The __cpufreq_driver_target() is external function which can be called on other file
>>>> so I must consider exception case.
>>>>
>>>> If send CPUFREQ_LOADCHECK noti after changed cpu frequency,
>>>> I think it is complicated and has quite a little difficulty.
>>>>
>>>> What is your opinion?
>>>
>>> What you can do is:
>>> - create another routine: cpufreq_governor_driver_target()
>>> - replace all __cpufreq_driver_target() from ondemand/conservative governors
>>> with this one
>>> - In cpufreq_governor_driver_target() call __cpufreq_driver_target() and
>>> take a note of new freq.
>>>
>>> Maybe you don't need to check the actual freq that is set (even
>>> that would be simple to implement), but what is requested.
>>>
>>
>> OK, I understand and will try to implement it.
>> Thanks.
>>
>> @Rafael?
>> If possible, I want to know the your opinion about this.
> 
> Well, to be honest, I don't like the whole thing.  The more changes you need
> to make to the common code to support it, the worse.
> 

To minimize the modification of cpufreq core, I implemented load_table debugfs file
by only using CPUFREQ_LOADCHECK and CPUFREQ_POSTCHANGE noti. So, I don't add additional
function for load_table debugfs file. I will send next version patch for load_table soon.

Best Regards,
Chanwoo Choi


      parent reply	other threads:[~2013-06-24  8:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  8:22 [PATCH v2] cpufreq: stats: Add 'load_table' debugfs file to show accumulated data of CPUs Chanwoo Choi
2013-06-20  9:03 ` Viresh Kumar
2013-06-20 10:45   ` Chanwoo Choi
2013-06-20 10:55     ` Viresh Kumar
2013-06-20 10:59       ` Chanwoo Choi
2013-06-20 11:18         ` Chanwoo Choi
2013-06-20 15:42           ` Viresh Kumar
2013-06-21  4:01             ` Chanwoo Choi
2013-06-21 13:13               ` Rafael J. Wysocki
2013-06-24  6:18                 ` Viresh Kumar
2013-06-24  9:39                   ` Rafael J. Wysocki
2013-06-24  9:41                     ` Viresh Kumar
2013-06-24 10:20                       ` Rafael J. Wysocki
2013-06-24 10:33                         ` Viresh Kumar
2013-06-24 11:00                           ` Rafael J. Wysocki
2013-06-24 11:18                             ` Chanwoo Choi
2013-06-24  8:32                 ` Chanwoo Choi [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=51C80409.1040806@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=rjw@sisk.pl \
    --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;
as well as URLs for NNTP newsgroup(s).