From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nigel Cunningham Date: Wed, 12 May 2004 02:16:02 +0000 Subject: Re: Hotplug events for system suspend/resume Message-Id: <200405121216.02787.ncunningham@linuxmail.org> List-Id: References: <20040511010015.GA21831@dhcp193.mvista.com> <20040511230001.GA26569@kroah.com> <40A17251.2000500@mvista.com> In-Reply-To: <40A17251.2000500@mvista.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Todd Poynor , Greg KH Cc: mochel@digitalimplant.org, linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Hi. Unless I'm missing something, this will break all existing implementations of S3 and S4 because they all freeze userspace processes prior to suspending drivers. They do this because they assume it is the responsibility of userspace to handle these actions prior to telling the kernel to suspend. In my mind, this approach is simpler and makes more sense: userspace should worry about userspace actions related to suspending before calling kernelspace. Kernel space should then only worry about saving and restoring driver states and should be transparent to user space. If at resume time, some devices have really gone away or appeared, hot[un]plugging events can call userspace then. One other point: If we have userspace calling kernelspace which calls userspace, won't we also have to be very careful about not setting up feedback loops? (Who knows what userspace will do in response to our unplug notification). Regards, Nigel ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel