From: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
rjw@rjwysocki.net, Gautham R Shenoy <ego@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, pc@us.ibm.com, anton@samba.org,
shreyas@linux.vnet.ibm.com, bsingharora@gmail.com,
mpe@ellerman.id.au, linux-api@vger.kernel.org
Subject: Re: [PATCH v8 6/6] cpufreq: powernv: Add sysfs attributes to show throttle stats
Date: Wed, 03 Feb 2016 21:54:41 +0530 [thread overview]
Message-ID: <56B229C9.4010909@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160203140600.GG3469@vireshk>
>
> And now that you have mentioned that to me, why shouldn't this stats
> directory be moved to debugfs ? :)
>
> We are never going to perform a store here, isn't it ? And is just for
> information, nothing more.
>
I would very much like to keep the throttle stats either in cpuX/cpufreq or
global cpufreq directory as these are populated by the platform cpufreq driver.
Today we don't have a requirement to a perform a store operation on these files
but we can have it in the future.
Thanks and Regards,
Shilpa
next prev parent reply other threads:[~2016-02-03 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1454442102-1229-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com>
2016-02-02 19:41 ` [PATCH v8 6/6] cpufreq: powernv: Add sysfs attributes to show throttle stats Shilpasri G Bhat
2016-02-03 8:27 ` Viresh Kumar
2016-02-03 8:42 ` Shilpasri G Bhat
2016-02-03 9:03 ` Viresh Kumar
2016-02-03 12:02 ` Gautham R Shenoy
2016-02-03 14:06 ` Viresh Kumar
2016-02-03 16:24 ` Shilpasri G Bhat [this message]
[not found] ` <56B229C9.4010909-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-02-04 1:51 ` 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=56B229C9.4010909@linux.vnet.ibm.com \
--to=shilpa.bhat@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=bsingharora@gmail.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=pc@us.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=shreyas@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).