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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 29 Mar 2008 14:56:03 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	"Darrick J. Wong" <djwong@...ibm.com>
Cc:	"Mark M. Hoffman" <mhoffman@...htlink.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	lm-sensors <lm-sensors@...sensors.org>
Subject: Re: [PATCH 1/2] Define sysfs interfaces for ibmaem driver

Hi Darrick,

On Fri, 28 Mar 2008 14:36:46 -0700, Darrick J. Wong wrote:
> Update sysfs interface documentation to include energy meters and power
> meter averaging intervals.
> 
> Signed-off-by: Darrick J. Wong <djwong@...ibm.com>
> ---
> 
>  Documentation/hwmon/sysfs-interface |   12 ++++++++++++
>  1 files changed, 12 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/hwmon/sysfs-interface b/Documentation/hwmon/sysfs-interface
> index f4a8ebc..85e6654 100644
> --- a/Documentation/hwmon/sysfs-interface
> +++ b/Documentation/hwmon/sysfs-interface
> @@ -328,6 +328,14 @@ curr[1-*]_input	Current input value
>  		Unit: milliampere
>  		RO
>  
> +**********
> +* Energy *
> +**********
> +
> +energy[1-*]_input		Instantaneous energy use

This doesn't make sense to me. Energy is a quantity, it exists
independently of time. An "instantaneous energy use" only makes sense
if you tell in what (presumably very small) amount of time the energy
was used... and then what you are measuring is not an energy but a
power, for which we already have an interface. Please clarify.

> +				Unit: microJoule
> +				RO
> +
>  *********
>  * Power *
>  *********
> @@ -336,6 +344,10 @@ power[1-*]_average		Average power use
>  				Unit: microWatt
>  				RO
>  
> +power[1-*]_interval		Power use averaging interval

Wouldn't power[1-*]_average_interval be clearer?

> +				Unit: milliseconds

Nitpicking for consistency: millisecond (no trailing s).

What values do you expect for this entry? I am wondering if it's safe
to use millisecond as a unit. Is it unlikely that a future chip will
support averaging intervals below the millisecond?

> +				RW
> +
>  power[1-*]_average_highest	Historical average maximum power use
>  				Unit: microWatt
>  				RO


-- 
Jean Delvare
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ