From: Greg KH <greg@kroah.com>
To: Amit Kachhap <amit.kachhap@linaro.org>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-pm@lists.linux-foundation.org, linaro-dev@lists.linaro.org,
patches@linaro.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, rob.lee@linaro.org
Subject: Re: [linux-pm] [RFC PATCH] thermal: Add support to report cooling statistics achieved by cooling devices
Date: Mon, 6 Feb 2012 16:18:18 -0800 [thread overview]
Message-ID: <20120207001818.GB30840@kroah.com> (raw)
In-Reply-To: <CAK44p22FWxiXyBA1zbiuO0cbDScTSMRSV9pFDDMxXsc43ebGpw@mail.gmail.com>
On Mon, Feb 06, 2012 at 03:16:17PM -0800, Amit Kachhap wrote:
> On 6 February 2012 09:03, Greg KH <greg@kroah.com> wrote:
> > On Mon, Feb 06, 2012 at 05:56:58PM +0100, Pavel Machek wrote:
> >> Hi!
> >>
> >> > Add a sysfs node code to report effective cooling of all cooling devices
> >> > attached to each trip points of a thermal zone. The cooling data reported
> >> > will be absolute if the higher temperature trip points are arranged first
> >> > otherwise the cooling stats is the cumulative effect of the earlier
> >> > invoked cooling handlers.
> >> >
> >> > The basic assumption is that cooling devices will bring down the temperature
> >> > in a symmetric manner and those statistics can be stored back and used for
> >> > further tuning of the system.
> >>
> >> /sys fs should be one-value-per-file, talk to gregkh.
> >
> > That's correct.
> >
> > Why not use debugfs for this instead?
> >
> > thanks,
> >
> > greg k-h
>
> Thanks Greg/Pavel for looking into the patch.
> Basically I checked the places where single sysfs entry is showing
> more then 1 output. And
> 1) /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
> 2) /sys/devices/system/cpu/cpu0/cpufreq/stats/trans_table
> are the places where the output is more than 1 value.
Yes, those are two known-bad files, whose files will change soon and
move to debugfs.
Just because you found 2, instead of the thousands of other properly
formatted files, does not mean you are allowed to create something like
this.
> Anyway I can enclose this sysfs inside CONFIG_THERMAL_COOLING_STATS macro.
No, you can not create it at all in sysfs, if you really need such a
large single file, use debugfs instead, that is what it is there for.
Again, one-value-per-file is the sysfs rule, and has been for a decade
now, please don't think this is a new thing.
greg k-h
next prev parent reply other threads:[~2012-02-07 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 9:21 [linux-pm][RFC PATCH] thermal: Add support to report cooling statistics achieved by cooling devices Amit Daniel Kachhap
2012-02-06 16:56 ` [linux-pm] [RFC " Pavel Machek
2012-02-06 17:03 ` Greg KH
2012-02-06 23:16 ` Amit Kachhap
2012-02-07 0:18 ` Greg KH [this message]
2012-02-07 18:26 ` Amit Kachhap
2012-02-07 7:09 ` Eduardo Valentin
2012-02-07 17:52 ` Amit Kachhap
2012-02-07 19:29 ` Eduardo Valentin
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=20120207001818.GB30840@kroah.com \
--to=greg@kroah.com \
--cc=amit.kachhap@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=patches@linaro.org \
--cc=pavel@ucw.cz \
--cc=rob.lee@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