linux-kernel - [PATCH 0/3] PM: Runtime PM and device PM QoS refinements

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201109242323.03474.rjw@sisk.pl>
Date:	Sat, 24 Sep 2011 23:23:03 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Linux PM mailing list <linux-pm@...ts.linux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"Linux-sh list" <linux-sh@...r.kernel.org>,
	Magnus Damm <magnus.damm@...il.com>,
	Kevin Hilman <khilman@...com>, jean.pihet@...oldbits.com,
	Ming Lei <tom.leiming@...il.com>
Subject: [PATCH 0/3] PM: Runtime PM and device PM QoS refinements

Hi,

On Wednesday, August 31, 2011, Rafael J. Wysocki wrote:
> Hi,
> 
> This patchset illustrates how device PM QoS may be used along with
> PM domains in my view.
> 
> Actually, it consists of two parts.  Namely, patches [1-3/5] seem to be
> suitable for 3.2, unless somebody hates them, but patches [4-5/5] are
> total RFC.  They haven't been tested, only compiled, so the use of them
> is not encouraged (they may kill your dog or make your cat go wild, or
> do something equally nasty, so beware).  Their purpose is to illustrate
> an idea that I'd like to discuss at the PM miniconference during the
> LPC.
> 
> [1/5] - Split device PM domain data into a "base" and additional fields
>         (one need_restore field at the moment, but the subsequent patches
>         add more fields).
> 
> [2/5] - Make runtime PM always release power.lock if power.irq_safe is set.
> 
> [3/5] - Add function for reading device PM QoS values safely.
> 
> [4/5] - Add governor function for stopping devices.
> 
> [5/5] - Add generic PM domain power off governor function.

I have updated patches [1-3] after receiving some feedback and the result
follows.  These patches are regarded as 3.2 material, if no one has
objections.

[1/3] - Split device PM domain data into a "base" and additional fields
        (one need_restore field at the moment).
 
[2/3] - Make runtime PM always release power.lock if power.irq_safe is set.
 
[3/3] - Add function for reading device PM QoS values safely.

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/