From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
cpufreq@vger.kernel.org, kyungmin.park@samsung.com,
myungjoo.ham@samsung.com
Subject: Re: [RESEND][PATCH] cpufreq: stats: Add 'load_table' sysfs file to show accumulated data of CPU
Date: Wed, 12 Jun 2013 13:05:09 +0200 [thread overview]
Message-ID: <2801243.ZfLEluCnpU@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpomwDonECPOPoSZvrOS+mRyNARX4Sk1XoEAGLXrOQQjYjA@mail.gmail.com>
On Wednesday, June 12, 2013 09:32:16 AM Viresh Kumar wrote:
> On 12 June 2013 03:44, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Wednesday, June 05, 2013 05:11:22 PM Chanwoo Choi wrote:
> >> This patch add new sysfs file to show previous accumulated data of CPU load
> >> as following path. This sysfs file is used to judge the correct system state
> >> or determine suitable system resource on user-space.
> >> - /sys/devices/system/cpu/cpu0/cpufreq/stats/load_table
> >>
> >> This sysfs file include following data:
> >> - Measurement point of time
> >> - CPU frequency
> >> - Per-CPU load
> >>
> >> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> >> Signed-off-by: Myungjoo Ham <myungjoo.ham@samsung.com>
> >> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> >
> > Well, first of all, there is the "one value per file" rule for sysfs attributes
> > which is evidently violated by this code.
>
> Even this was enclosed in CONFIG_CPU_FREQ_STAT_DETAILS,
> so even sysfs isn't that bad as we already had something similar here.
Yes, we did, and yes, it was a mistake. It should have been in debugfs from
the very beginning.
> > Second, this looks like a feature needed to handle one particular platform, so
> > why do you want to add it to the cpufreq core?
>
> I really felt this would be useful to others. They can track the load on
> all cores for some time and that will really be useful. People can
> understand their loads and system more easily with this patch in.
If it were in debugfs, I'd have no objections.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-06-12 10:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 8:11 [RESEND][PATCH] cpufreq: stats: Add 'load_table' sysfs file to show accumulated data of CPU Chanwoo Choi
2013-06-07 10:23 ` Viresh Kumar
2013-06-10 12:13 ` Chanwoo Choi
2013-06-11 5:06 ` Viresh Kumar
2013-06-11 5:19 ` Chanwoo Choi
2013-06-11 5:22 ` Viresh Kumar
2013-06-11 6:10 ` Chanwoo Choi
2013-06-11 22:14 ` Rafael J. Wysocki
2013-06-12 0:51 ` Chanwoo Choi
2013-06-12 4:02 ` Viresh Kumar
2013-06-12 11:05 ` Rafael J. Wysocki [this message]
2013-06-14 2:11 ` Chanwoo Choi
2013-06-14 4:11 ` Viresh Kumar
2013-06-14 12:48 ` Rafael J. Wysocki
2013-06-14 14:49 ` Viresh Kumar
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=2801243.ZfLEluCnpU@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--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