On Friday, February 03, 2012, Pihet-XID, Jean wrote: > Looping in linux-pm > > On Fri, Feb 3, 2012 at 1:14 AM, Venkatesh Pallipadi <venki@xxxxxxxxxx> wrote: > > Looks like change "PM QoS: Move and rename the implementation files" > > made pm_qos depend on CONFIG_PM which depends on > > PM_SLEEP || PM_RUNTIME > > > > That breaks CPU C-states with kernels not having these CONFIGs, causing CPUs > > to spend time in Polling loop idle instead of going into deep C-states, > > consuming way way more power. This is with either acpi idle or intel idle > > enabled. > > > > Either CONFIG_PM should be enabled with any pm_qos users or > > the !CONFIG_PM pm_qos_request() should return sane defaults not to break > > the existing users. Here's is the patch for the latter option. > I think the real question is whether PM QoS should be functional in > all cases (as is ACPI) or whether only if certain options are set > (CONFIG_PM). > In the current code if CONFIG_PM is not enabled, a dummy PM QoS API is > provided as function stubs in order for the build to succeed. > > Rafael, Mark, > What do you think? Should PM QoS be enabled in all cases? Are there > any known dependencies with CONFIG_PM? At least we should keep the current behavior to avoid breaking things for now. We can change that in the next cycle, however, if everyone agrees, but more carefully. The patch has been applied to linux-pm/linux-next and will be pushed to Linus early next week. Thanks, Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/linux-pm
