On Sun, Aug 08, 2010 at 03:40:28PM +0300, Felipe Contreras wrote:
Indeed they are, given the way you quoted small portions of them. ;-)
These would be buggy PM-driving applications. Of course, any type of
application might have bugs, including PM-driving applications.
I did indeed exclude this category by saying "power-optimized applications
are those PM-driving applications that have been aggressively tuned
to reduce power consumption." The reason I excluded this case is that
that there are a number of cases where removing the PM-driving attribute
could destroy the power optimization.
If you have an example power-optimized application that retains its
power-optimized property despite lacking PM-driving privileges, please
put it forward. In doing so, please keep two things in mind:
1. The definition of power-optimized is more aggressive than many
people are used to -- look at http://lkml.org/lkml/2010/8/4/409
and search for "POWER-OPTIMIZED APPLICATIONS".
2. In a number of the implementations that do not use suspend blockers,
-all- applications are in effect PM-driving applications.
So it is quite possible that different people are using subtly
different flavors of the "PM-driving applications" definition.
For example, an Android person might consider a application to
be PM-driving only if it is permitted to use suspend blockers,
while a Maemo person might consider an application to be
PM-driving if it had permission to invoke pm_qos functions.
If these two hypothetical people each try to apply their
definition of PM-driving to each others' platforms, they will
likely have severe problems communicating with each other,
right? ;-)
But if you do have a good example, perhaps I will need to change my
definition of power-optimized application.
In fact, you might have noticed that the proponents of each platform
have been quite persistent in shouting past each other from the warmth
and security of their own particular viewpoints. ;-)
Thanx, Paul
--
