linux-kernel - Re: [RFC v01 0/3] Power Capping Framework

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, 3 Aug 2013 06:29:09 +0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC v01 0/3] Power Capping Framework

On Fri, Aug 02, 2013 at 11:08:49AM -0700, Srinivas Pandruvada wrote:
> - A uniform sys-fs interface for all devices which can offer power capping

There is no "-" in sysfs please.

> - A common API for drivers, which will avoid code duplication and easy
> implementation of client drivers.
> 
> Once this framework is approved, we will submit a RAPL client driver using this
> framework.

No, you need users of a framework in order for it to be approved, we
don't add infrastructure without users.

Especially as what usually happens is, when you add actual users, the
framework changes to fix the bugs found in it :)

Ideally you will have more than one client driver submitted, as a
"framework" for just one driver seems a bit odd, don't you think?

Also, you add lots of new sysfs files, those need to be documented in
Documentation/ABI/ with this series.

thanks,

greg k-h
--
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/