linux-kernel - Re: [RFC][PATCH] PM: Make PM core handle device registrations concurrent with suspend/hibernation

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 5 Mar 2008 17:16:29 +0100
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	pm list <linux-pm@...ts.linux-foundation.org>,
	Alexey Starikovskiy <astarikovskiy@...e.de>,
	Pavel Machek <pavel@....cz>,
	LKML <linux-kernel@...r.kernel.org>,
	Marcel Holtmann <marcel@...tmann.org>
Subject: Re: [RFC][PATCH] PM: Make PM core handle device registrations
 concurrent with suspend/hibernation

On Wed, 5 Mar 2008 11:03:52 -0500 (EST),
Alan Stern <stern@...land.harvard.edu> wrote:

> There might still be logical problems, of course...  We need to add a
> mechanism for reordering the dpm_active list when device_move() is
> called.  But first we need to get in touch with the people using
> device_move() -- basically just Marcel and Cornelia -- and see what
> sort of mechanism they will need.

On s390 we currently don't do anything suspend related at all - I'd
need to think about that. (I use device_move() to reflect topology
changes on the (virtual) hardware, so I'd guess the "don't suspend
parent before child rule" should still apply afterwards. But of course,
that also depends on what we actually need to do on the parent's bus and
what on the child's bus.)
--
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/