Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752782Ab0FRF4r (ORCPT ); Fri, 18 Jun 2010 01:56:47 -0400 Received: from vms173011pub.verizon.net ([206.46.173.11]:43226 "EHLO vms173011pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752355Ab0FRF4q (ORCPT ); Fri, 18 Jun 2010 01:56:46 -0400 Date: Fri, 18 Jun 2010 01:56:27 -0400 (EDT) From: Len Brown X-X-Sender: lenb@localhost.localdomain To: Victor Lowther Cc: Linux Power Management List , Linux Kernel Mailing List , "linux-acpi@vger.kernel.org" Subject: Re: [linux-pm] RFC: /sys/power/policy_preference In-reply-to: Message-id: References: <0F1C0B07-60D6-405B-890B-F9C320820CA5@gmail.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-version: 1.0 Content-type: MULTIPART/MIXED; BOUNDARY="8323328-1548819180-1276840588=:7628" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1823 Lines: 43 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-1548819180-1276840588=:7628 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT 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 --8323328-1548819180-1276840588=:7628-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/