On Mon, Apr 18, 2005 at 09:39:19AM -0600, Jordan Crouse wrote: --> snip > > > I personally have some concerns over too much userspace interaction. > > I think these decisions are too device specific, and if we don't take > > responsibility for them, then the layers above the kernel may not be > > able to properly handle it. > > I generally favor the "user knows best" policy. As developers, we will > make the best overall power management decisions for our drivers > (timeouts, system state transitions, etc, etc...), but should allow for > a facility for the user to override these if they so choose (possibly > through the policy manager). We can even go so far as to make the > framework disabled by default in the kernel, so that one has to go in, > specifically choose it, and thereby take on the additional risk. I agree. As a thought, what if we included some suggested power attribute configurations as module data (much like we do with pci device IDs now)? This would allow the driver developer to pass this information up to userspace, without imposing any policy. The default settings could be performance orriented and then when userspace starts up it could tell the policy manager to slow things down. In general, it seems to make sense for userspace to tell the kernel about policy preferences, but then have the kernel execute those decisions. If we were to ship suggested policy options inside of driver modules, then driver developers could ensure the user is at least aware of typical policy configuration values. Also, it might be useful to distribute a set of userspace power management tools. We could call it something like "hardware-utils" and have it handle PM policy and other userspace driver core issues. Thanks, Adam
