ext Alan Cox wrote:
Be that as it may the question of how you manage a naughty app is a good
one. Historically we've managed them for network abuse, memory abuse, cpu
use abuse, access rights, but not yet power.
Whether that looks like
setrlimit(pid, LIMIT_CHARGE, 150mWH);
or
setrlimit(pid, LIMIT_POWER, 150mW);
or something else is the question.
Either way, this will require a detailed model of the system in terms of
latency, throughput, current consumption and heat generation.
Which can be provided only by the HW manufacturer.
But, should such model be available (and we have some form of it for the
OMAP3 in N900), then it can be abstracted through generic interfaces,
which accept constraints and produce the selected target state
(typically a vector of states for each sub component).
igor
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
