| 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: Fri, 02 Aug 2013 17:10:44 -0700 From: Joe Perches <joe@...ches.com> To: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com> Cc: linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org Subject: Re: [RFC v01 1/3] PowerCap: Documentation 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? -- 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