> > Do you think I should modify schedule() to do freezing automatically?
> > I wanted to keep my hands off hot paths... I'd rather not do that.
>
> No, I just suspect you could freeze them _while_ they sleep by just
> picking up their information from the normal save area.
>
> Yeah, I know, Linux tends to save a lot of the process stuff implicitly on
> the stack, so maybe that ends up being harder than it sounds, and you've
> done it for other tasks with the signal handler code instead, but you
> _should_ be able to do it without any signal handler hackery by just
> saving off their kernel stack and the stuff in the thread structure.
I need to know more than they are sleeping. I also know they are
sleeping *without holding any semaphores*. I need working system to be
able to save state to disk. That's why I hacked it into signal
handler.
Pavel
-- Casualities in World Trade Center: ~3k dead inside the building, cryptography in U.S.A. and free speech in Czech Republic. - 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/