Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8)

Alan Stern
2010-05-27T23:02:31Z

Matthew:

Remind me why the idle/QOS power management approach won't work here.

If the difficulty is untrusted apps preventing the system from being
idle, why not assign them to QoS(NONE) as Thomas suggested?

If the difficulty is that some untrusted apps need to receive wakeup
events, why not just decree that this is not allowed? It seems
reasonable that if you can't trust a program then you shouldn't allow
it to wake up the system.

If the difficulty is that some trusted apps need to do CPU-burning
things like drawing bouncing cows in the background, why not break
these apps into two processes or threads? One can be trusted and
receive all the wakeup events, and the other can be untrusted and draw
all the cows it likes. We're only talking about trusted apps, most of
which would be controlled by Google, so the conversion shouldn't be too
hard.

If the difficulty is that ACPI-based systems can't use idle/QOS PM
effectively... well, so be it. We don't have to solve every problem
in the world right away, and just now we're mainly concerned about
helping the Android people.

Alan Stern