Actually, what I was thinking is that if you use the swsusp infrastructure to
suspend all processes, all dma, quiesce the heck out of the devices, and
_then_ try to move the kernel... Well, you at least have a much more
controlled problem. Yeah, it's pretty darn intrusive, but if you're doing
"suspend to ram" perhaps the downtime could be only 5 or 10 seconds...
I don't think suspend to ram for a memory hotplug remove would be acceptable to
users. The other methods add some complexity to the kernel, but are transparent
to userspace. Downtime of 5 to 10 seconds is really quite a bit of downtime.
I don't know how much of the problem that leaves unsolved, though.
It would still require a remappable kernel. And seems intuitively to be wrong
to me. But if you want to try it out I won't stop you. It might even work.
-
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]
