linux-kernel - [PATCH 0/3] PM / Domains: Fix device stop and domain power off governor functions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Apr 2012 23:49:26 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Linux PM list <linux-pm@...r.kernel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, Kevin Hilman <khilman@...com>,
	Magnus Damm <magnus.damm@...il.com>, linux-sh@...r.kernel.org,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	markgross@...gnar.org, Jean Pihet <j-pihet@...com>
Subject: [PATCH 0/3] PM / Domains: Fix device stop and domain power off governor functions

Hi all,

It turns out that the PM domains device stop and domain power off governor
functions I invented some time ago don't really make sense, because they
should only decide whether or not the resulting low-power state will be
too deep and that only depends on latencies.  In particular, the time
when devices have been suspended doesn't really matter here, so the
results returned by those functions shouldn't depend on it either (as it
shouldn't depend on any "break even" values that only make sense when we
know how much time in advance the device is going to be used, but this
information is not related to the PM QoS latency constraint).

If this functions are fixed (patches [1/3] and [2/3]), then some ugly
computations can be removed from rpm_suspend() and other places and the
whole framework can be simplified quite a bit (patch [3/3]).

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/