lkml.org 
[lkml]   [2002]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: suspend-to-{RAM,disk} for 2.5.17


On Wed, 22 May 2002, Pavel Machek wrote:
>
> 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.

Sorry, I should have been more clear. I think the signal handler approach
is fine for user processes, I was just wondering why you needed anything
like that for kernel threads..

When a kernel thread is sleeping, I don't see that it has much state at
all: it will be re-started anyway on the next boot, and I don't see it
having any "state".

(I didn't think it through enough - never mind saving the stack page,
because I don't think there is anything at all interesting there to save).

Linus

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:26    [W:0.064 / U:0.668 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site