From: Chanwoo Choi <cw00.choi@samsung.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, 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: Thu, 20 Jun 2013 19:59:57 +0900 [thread overview]
Message-ID: <51C2E0AD.8060208@samsung.com> (raw)
In-Reply-To: <CAKohpomx54Y3WVToYP0nOw-hsxKzGjp2nyfzWf5bo1s530Yg1w@mail.gmail.com>
On 06/20/2013 07:55 PM, Viresh Kumar wrote:
> On 20 June 2013 16:15, Chanwoo Choi <cw00.choi@samsung.com> wrote:
>> Yes, freq->old is same freq->new.
>>
>> The cpufreq gorvernor(dbs_check_cpu()) send CPUFREQ_LOADCHECK noti
>> right after calculating CPUs load, regardless of changing CPU frequency.
>> So, I use only freq->old value without using freq->new because load_table
>> debugfs file need current cpu frequency.
>>
>> Now, I can't think of any proper usage for freq->new.
>> Do you have good way for using freq->new to include more useful data in load_table?
>
> This information might be interesting.. At what load, we moved from
> which freq to which one..
>
> Just see if you can add the notification after frequency has been
> changed.
>
OK, I'll modify it and send test result. Thanks.
Best Regards,
Chanwoo Choi
next prev parent reply other threads:[~2013-06-20 11:00 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 [this message]
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
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=51C2E0AD.8060208@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