| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 05 Aug 2013 12:52:08 -0700 From: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com> To: Jonathan Corbet <corbet@....net> CC: linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org Subject: Re: [RFC v01 1/3] PowerCap: Documentation On 08/05/2013 12:09 PM, Jonathan Corbet wrote: > On Fri, 2 Aug 2013 11:08:50 -0700 > Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com> wrote: > >> +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. > Sorry if I'm slow, but... power is an instantaneous quantity, so why would > you use a counter for it? And why would you want to reset it to zero? It is an instantaneous value. When I say counter, either in hardware or in driver somewhere, it is reading energy and using a time delta and continuously updating this value. Reset to zero will allow user space to reset its internal energy counter used to calculate power. Our hardware at this time can only provide energy_uj at this time, added power_uw for some future devices. This was suggested in internal reviews. But based on feedback, we can drop this attribute totally, till we have a device needing this. > Thanks, > > jon > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists