Hi Pavel,
Pavel Machek wrote:
Should be very easy to solve with one semaphore. Simply make swsusp
wait until all migrations are done.
This may not be needed. If I understand things correctly, the system
won't suspsend until all tasks have returned from system calls and end
up in the refrigerator. So if a memory migration is running when
someone tries to suspend the system, the suspend won't
occur until the memory migration system call returns.
Is that correct?
What happens if a system call calls schedule() (or otherwise gets blocked,
e. g. by trying to obtain a semaphore?)
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
[email protected] [email protected]
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
