I'm running a power management session at the Linux Plumbers Conference this year. Unlike most traditional conferences where the aim is to present new solutions, LPC focuses on discussing the problems that we haven't completely solved yet. This has been an especially interesting year in the field. We've landed the infrastructure for generic runtime power management, glued that into PCI and started implementing that at the driver level. pm_qos is being reworked to improve performance and scalability as we start seeing more drivers that need to express their own constraints. And, of course, we had the wakelock/suspend blockers conversation that didn't end in a terribly satisfactory manner, although Rafael is now working on an implementation that presents equivalent functionality with a different userspace API. Runtime full-system suspend isn't solved yet either - the current cpuidle-based solution doesn't work well on multicore systems. And maybe we could be more aggressive still by looking at reclocking more system components on the fly even if the existing interfaces don't allow that. Do we have all the hooks we need to identify which system resources are being used? Are we doing the best we can in terms of avoiding trading off performance for power savings? Head to http://www.linuxplumbersconf.org/2010/ocw/events/LPC2010MC/proposals to add a suggestion for a topic to be discussed at the miniconference. It's also possible to submit a proposal for the main presentation tyou have menrelated that you think would be appropriate for a wider audience, then please propose it there as well. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
