linux-kernel - Re: [linux-pm] RFC: /sys/power/policy

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]

Message-id: <alpine.LFD.2.00.1006180149120.7628@localhost.localdomain>
Date:	Fri, 18 Jun 2010 01:56:27 -0400 (EDT)
From:	Len Brown <lenb@...nel.org>
To:	Victor Lowther <victor.lowther@...il.com>
Cc:	Linux Power Management List <linux-pm@...ts.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: [linux-pm] RFC: /sys/power/policy_preference

On Thu, 17 Jun 2010, Victor Lowther wrote:

> > The idea here is to not require user-space to need updating
> > whenever a future knob is invented.  We can do a great job
> > at documenting the past, but a poor job of documenting the future:-)
> 
> Well, I would suggest that the habit of not documenting what is
> happening with power management in the kernel needs to change, then.

Actually some of the knobs I showed in the examples
have been documented for *years*, yet are ignored
by user-space today.  I don't want to insult user-space
programmers, but the reality is that simpler is usually better.

> Having the documentation and example code for how to tweak the various
> power management settings from userspace is inherently more flexible
> than trying to expose a single knob from the kernel to userspace for
> power management, with little loss of flexibility.

Yes, the ultimate in flexibility is to update user-space whenever
some new driver or new knob appears in the kernel.  I'm not proposing
that ability be taken away.  I'm proposing that in many cases it
is unnecessary.

The idea is to have the ability to add something to the 
kernel and avoid the need to make any change to user-space.

thanks,
-Len Brown, Intel Open Source Technology Center