From: Joe Perches <joe@perches.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [RFC v01 1/3] PowerCap: Documentation
Date: Fri, 02 Aug 2013 17:10:44 -0700 [thread overview]
Message-ID: <1375488644.2034.150.camel@joe-AO722> (raw)
In-Reply-To: <1375466932-11842-2-git-send-email-srinivas.pandruvada@linux.intel.com>
On Fri, 2013-08-02 at 11:08 -0700, Srinivas Pandruvada wrote:
> Added power cap framework documentation. This explains the use of power capping framework,
> sys-fs and programming interface.
[]
> +Power Zone Attributes
> +=================================
> +Monitoring attributes
> +----------------------
> +
> +energy_uj (rw): Current energy counter in micro-joules. Write to energy counter
> +resets the counter to zero. If the counter can not be reset, then this attribute
> +is read-only.
> +
> +max_energy_range_uj (ro): Range of the above energy counter in micro-joules.
> +
> +power_uw (rw): Current power counter in micro-watts. Write to this counter
> +resets the counter to zero. If the counter can not be reset, then this attribute
> +is read-only.
> +max_power_range_uw (ro): Range of the above energy counter in micro-watts.
> +
> +It is possible that some domains can have both power and energy counters and
> +ranges, but at least one is mandatory.
Given that the ranges seem to be u64s, perhaps the
lower bounds are too high. Why not nano/pico/fempto
watts/joules/seconds?
next prev parent reply other threads:[~2013-08-03 0:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 18:08 [RFC v01 0/3] Power Capping Framework Srinivas Pandruvada
2013-08-02 18:08 ` [RFC v01 1/3] PowerCap: Documentation Srinivas Pandruvada
2013-08-03 0:10 ` Joe Perches [this message]
2013-08-03 0:23 ` Srinivas Pandruvada
2013-08-03 0:25 ` Joe Perches
2013-08-05 19:09 ` Jonathan Corbet
2013-08-05 19:52 ` Srinivas Pandruvada
2013-08-02 18:08 ` [RFC v01 2/3] PowerCap: Add class driver Srinivas Pandruvada
2013-08-02 22:43 ` Joe Perches
2013-08-03 0:06 ` Srinivas Pandruvada
2013-08-02 18:08 ` [RFC v01 3/3] PowerCap: Added to drivers build Srinivas Pandruvada
2013-08-02 22:29 ` [RFC v01 0/3] Power Capping Framework Greg KH
2013-08-02 23:52 ` Srinivas Pandruvada
2013-08-03 0:53 ` Greg KH
2013-08-04 19:36 ` Arjan van de Ven
2013-08-02 22:30 ` Greg KH
2013-08-02 22:33 ` Joe Perches
2013-08-02 22:50 ` Greg KH
2013-08-03 0:03 ` Srinivas Pandruvada
2013-08-03 0:54 ` Greg KH
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=1375488644.2034.150.camel@joe-AO722 \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
/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
all inboxes | Powered by JetHome®