> 1. You can instead put the stuff in apmd - so when it sees a resume the
> APM daemon configures your disk back
>
> 2. You wake a thread (or let an existing thread) do it. The thread can
> sleep even though the irq cannot.
>
> Making apmd handle it seems "right" since it keeps it in user space
Making apmd do it should be easy - new versions of apmd should allow
you to run arbitrary commands after events.
Only problem with "going userspace" is: what happens if apmd is
swapped out? Then you need to read disk in order to swap it in. But
you can not read disk, because it is missconfigured, now...
Looks like it is not the way to go. :-(
Pavel
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/