linux-kernel - [RFC][RFP] LPC2016 Thermal MC

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>] [day] [month] [year] [list]

Message-ID: <20160503035548.GA19699@localhost.localdomain>
Date:	Mon, 2 May 2016 20:55:49 -0700
From:	Eduardo Valentin <edubezval@...il.com>
To:	Linux PM <linux-pm@...r.kernel.org>,
	Rui Zhang <rui.zhang@...el.com>
Cc:	caesar.wang@...k-chips.com, wxt@...k-chips.com, j-keerthy@...com,
	punit.agrawal@....com, viresh.kumar@...aro.org, wni@...dia.com,
	Srikar Srimath Tirumala <srikars@...dia.com>,
	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
	Lina Iyer <lina.iyer@...aro.org>, rjw@...ysocki.net,
	len.brown@...el.com, LKML <linux-kernel@...r.kernel.org>
Subject: [RFC][RFP] LPC2016 Thermal MC

Linux-pm,

As a continuation of the work done in 2015, I am proposing this year a
micro conference (MC) to gather thermal interested parties to discuss
improvements to the thermal subsystem [1]. Last year, I believe it was a
success in terms of achieving the goal of creating awareness, however, I
believe we need to continue improving the design and architecture of the
subsystem by listening how engineers are using it in their use cases.

Clearly, more and more I hear engineers looking for a better solution
for userspace driven policies. For this reason, I am proposing the
following agenda:

  * Sensor API: 
    * Current sensor feature support: what is really in use. 
    * interaction with other subsystems: IIO and hwmon, path to consolidation
  * Userspace governors:
    * What is currently existing
    * What feature are controlled by userspace governors
  * Effective userspace notification mechanism
    * Existing mechanism for notification
    * GAPs in notification needed to be covered
    * Policy configuration and interaction with userspace 
  * Cooling devices
    * Userspace listeners for cooling device state transition
    * Userspace cooling devices

If you are interested and have a good use case description to be discussed
within to above topics, please add your name to the list in the wiki, and
sign up for driving one of the topics. It would be nice to conclude the
MC with a list of practical required changes in the subsystem, based on
real use case scenarios.

I know the MC has a time limitation and we can probably also progress by
discussing code in the mailing list. However, I also believe it is important
to have a face to face discussion to better understand the use cases that
are not covered today.

Also, if you believe another topic needs to be covered, please, do not
hesitate to add it to the list.

Note: If you believe I forgot to copy someone, please help me to
properly make sure the message reaches the right quorum.

BR,

Eduardo Valentin

[1] - http://wiki.linuxplumbersconf.org/2016:thermal#proposed_topics_tentative