Messages in this thread | | | From | Nigel Cunningham <> | Subject | Re: Hotplug events for system suspend/resume | Date | Wed, 12 May 2004 12:16:02 +1000 |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |